-
Notifications
You must be signed in to change notification settings - Fork 6k
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
[Dashboard] Add dashboard multi-node churn test #11768
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
t = threading.Thread(target=cluster_chaos_monkey, daemon=True) | ||
t.start() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could consider using a ray actor for this as well
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@edoakes I like that idea. What's the best way to force my actor to live on the head node? Otherwise I'm concerned that it'll get destroyed by a node getting taken down (although I guess it would then be restarted on a node that's still up).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mfitton you can create a custom resource on the head node and target that resource with Actor.options(resources=xxx)
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
t = threading.Thread(target=cluster_chaos_monkey, daemon=True) | ||
t.start() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mfitton you can create a custom resource on the head node and target that resource with Actor.options(resources=xxx)
.
@mfitton lint is failing: |
…n test longer again now that I realized that was not the issue.
Why are these changes needed?
Adds a test to the dashboard that makes sure it continues to correctly function while a thread adds and removes nodes from the cluster at random.
This test had another line to test the node summary endpoint, but that currently causes a failure. Actually fixing this issue will be the subject of another PR. For the time being, this line is omitted.
Related issue number
Checks
scripts/format.sh
to lint the changes in this PR.