-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
[autoscaler] run setup commands with restart_only=True #13836
[autoscaler] run setup commands with restart_only=True #13836
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.
Also do this for init_commands
in autoscaler.py
(WORKERS)
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.
TODO(ilr): Make sure to validate with workers!
@AmeerHajAli I'm not sure what I should do with respect to worker nodes, I just realized that we don't have a field in
|
This is a good catch @ijrsvt. Lets go with option 1 for now. |
287a6b7
to
c0e193f
Compare
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.
haven't tried this out but looks fine - thanks @ijrsvt ! |
@richardliaw , can you please merge? |
…roject#13836)" This reverts commit a522509.
Why are these changes needed?
The Docker Command Runner may restart containers, requiring
setup_commands
to be re-run.NOTE: This does not apply to workers at the moment, as per #13861
Related issue number
Closes #13587
Checks
scripts/format.sh
to lint the changes in this PR.