-
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
Introduce file_mounts_sync_continuously cluster option #9544
Merged
Merged
Changes from 1 commit
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
93ed55d
Separate out file_mounts contents hashing into its own separate hash
alanwguo 26d186e
add test and default value for file_mounts_sync_continuously
alanwguo 6c0ca89
format code
alanwguo 59052a3
Update comments
alanwguo 0d6ebd1
Add param to skip setup commands when only file_mounts content change…
alanwguo 094262c
Refactor so that runtime_hash retains previous behavior
alanwguo d7f6461
fix issue with hashing a hash
alanwguo e0e1080
Merge branch 'master' into file-mounts-continous
alanwguo 37dd9b6
fix bug where trying to set contents hash when it wasn't generated
alanwguo 3c6f798
Merge branch 'master' into file-mounts-continous
alanwguo 415a32e
Fix lint error
alanwguo 108059d
clear out provider between tests to get rid of flakyness
alanwguo ca7b27d
reduce chance of race condition from node_launcher launching a node i…
alanwguo File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Refactor so that runtime_hash retains previous behavior
runtime_hash is almost identical as before this PR. It is used to determine if setup_commands need to run file_mounts_contents_hash is an additional hash of the file_mounts content that is used to detect when only file syncing has to occur. Note: runtime_hash value will have changed from before the PR because we hash the hash of the contents of the file_mounts as a performance optimization
- Loading branch information
commit 094262c4b9ac514e0c2cec866801a4cb62981236
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
What's the reason we need to check the inner hash and not just the runtime one?
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.
So when the contents of the head node's file_mounts change, the files will be synced to the worker nodes.
This behavior should be the same as before since previously, the contents hash were included with the runtime hash.
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.
One behaviour I'm concerned with is whether "ray up" will still work if continuous_sync mode is on. If I understand correctly, that won't update the cluster if only files have changed right?
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.
ah I see, in that case the rsync will still happen but the setup commands wont run. I'll make a change so that it only doesn't run setup commands when update is called in the monitor.py flow.