Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

If no local scheduler receives actor notification, retry. #393

Closed
wants to merge 1 commit into from
Closed

If no local scheduler receives actor notification, retry. #393

wants to merge 1 commit into from

Conversation

robertnishihara
Copy link
Collaborator

This may address #362.

for _ in range(num_retries):
num_recipients = worker.redis_client.publish(
"actor_notifications", actor_id.id() + local_scheduler_id)
if num_recipients == 1:
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't quite work because all of the local schedulers in the cluster will receive this publish message.

We could separate this into two publish message:

  • One targeted at the local scheduler that is supposed to create the actor.
  • One targeted at all local schedulers to notify them of the existence of a new actor.

@AmplabJenkins
Copy link

Merged build finished. Test PASSed.

@AmplabJenkins
Copy link

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/396/
Test PASSed.

@robertnishihara
Copy link
Collaborator Author

Closing for now because this fix doesn't quite work. However, the underlying problem remains, so some fix will be needed.

@robertnishihara robertnishihara deleted the possibleactorfix branch May 15, 2017 07:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants