-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
[air] Add RunConfig.storage_path
to replace SyncConfig.upload_dir
and RunConfig.local_dir
.
#33463
Conversation
Signed-off-by: Kai Fricke <[email protected]>
Signed-off-by: Kai Fricke <[email protected]>
Signed-off-by: Kai Fricke <[email protected]>
Signed-off-by: Kai Fricke <[email protected]>
Signed-off-by: Kai Fricke <[email protected]>
Signed-off-by: Kai Fricke <[email protected]>
Signed-off-by: Kai Fricke <[email protected]>
Signed-off-by: Kai Fricke <[email protected]>
Signed-off-by: Kai Fricke <[email protected]>
Signed-off-by: Kai Fricke <[email protected]>
Signed-off-by: Kai Fricke <[email protected]>
Signed-off-by: Kai Fricke <[email protected]>
storage_path
RunConfig.storage_path
to replace SyncConfig.upload_dir
and RunConfig.local_dir
.
Signed-off-by: Kai Fricke <[email protected]>
Signed-off-by: Kai Fricke <[email protected]>
Signed-off-by: Kai Fricke <[email protected]>
Signed-off-by: Kai Fricke <[email protected]>
Signed-off-by: Kai Fricke <[email protected]>
Signed-off-by: Kai Fricke <[email protected]>
Signed-off-by: Kai Fricke <[email protected]>
Signed-off-by: Kai Fricke <[email protected]>
Signed-off-by: Kai Fricke <[email protected]>
# Conflicts: # python/ray/tune/execution/trial_runner.py
Signed-off-by: Kai Fricke <[email protected]>
Signed-off-by: Kai Fricke <[email protected]>
This reverts commit 602eac4.
@@ -116,13 +116,22 @@ | |||
STDOUT_FILE = "__stdout_file__" | |||
STDERR_FILE = "__stderr_file__" | |||
|
|||
|
|||
def _get_defaults_results_dir() -> str: |
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.
[not related to this PR] in the future, this file and other file like trial.py
should really move to an execution specific folder rather than under tune
.
Signed-off-by: Kai Fricke <[email protected]>
Signed-off-by: Kai Fricke <[email protected]>
Looks like there is one related test failure? Also would be good to link the launch doc as well, for an understanding of gradual rollout. Thanks! |
This reverts commit 4a53fa2.
Signed-off-by: Kai Fricke <[email protected]>
Following #33463, this PR updates our tests, examples, and docs to use the new `storage_path` API. The only locations where we continue to use the `local_dir` statement are tests where we specify both a local dir and a remote dir. For these tests, we can move to an environment-variable based wrapper in the future. Signed-off-by: Kai Fricke <[email protected]>
…#34263) Following ray-project#33463, this PR updates our tests, examples, and docs to use the new `storage_path` API. The only locations where we continue to use the `local_dir` statement are tests where we specify both a local dir and a remote dir. For these tests, we can move to an environment-variable based wrapper in the future. Signed-off-by: Kai Fricke <[email protected]>
… and `RunConfig.local_dir`. (ray-project#33463) Pending acceptance of ray-project/enhancements#27, this PR changes the input API to configure persistent storage paths in Ray AIR and Ray Tune. In a nutshell: - We have a unified setting `RunConfig.storage_path` that can be set either to a local dir or a remote path. - Setting the storage path to a cloud or NFS URI (e.g., `s3://`, or `file://` that points to a NFS mount). In these cases, data will be first written to a local cache dir on the worker, and then synced to a subdirectory in the storage path designated by `<experiment_name>/<trial_name>/`. - Setting the storage path to a purely local URI (e.g., `/home/foo/ray_results`). In this mode, trial data is synced to the head node via the object store. We would generally recommend using a remote storage path or shared directory instead. This PR deprecates existing input API arguments, and introduces the new `storage_path` configuration. The changes are fully backwards compatible. This is proven by the fact that this PR only changes very few private API calls in the test suites. All tests and examples are expected to continue to work. Signed-off-by: Kai Fricke <[email protected]> Signed-off-by: elliottower <[email protected]>
…#34263) Following ray-project#33463, this PR updates our tests, examples, and docs to use the new `storage_path` API. The only locations where we continue to use the `local_dir` statement are tests where we specify both a local dir and a remote dir. For these tests, we can move to an environment-variable based wrapper in the future. Signed-off-by: Kai Fricke <[email protected]> Signed-off-by: elliottower <[email protected]>
… and `RunConfig.local_dir`. (ray-project#33463) Pending acceptance of ray-project/enhancements#27, this PR changes the input API to configure persistent storage paths in Ray AIR and Ray Tune. In a nutshell: - We have a unified setting `RunConfig.storage_path` that can be set either to a local dir or a remote path. - Setting the storage path to a cloud or NFS URI (e.g., `s3://`, or `file://` that points to a NFS mount). In these cases, data will be first written to a local cache dir on the worker, and then synced to a subdirectory in the storage path designated by `<experiment_name>/<trial_name>/`. - Setting the storage path to a purely local URI (e.g., `/home/foo/ray_results`). In this mode, trial data is synced to the head node via the object store. We would generally recommend using a remote storage path or shared directory instead. This PR deprecates existing input API arguments, and introduces the new `storage_path` configuration. The changes are fully backwards compatible. This is proven by the fact that this PR only changes very few private API calls in the test suites. All tests and examples are expected to continue to work. Signed-off-by: Kai Fricke <[email protected]> Signed-off-by: Jack He <[email protected]>
…#34263) Following ray-project#33463, this PR updates our tests, examples, and docs to use the new `storage_path` API. The only locations where we continue to use the `local_dir` statement are tests where we specify both a local dir and a remote dir. For these tests, we can move to an environment-variable based wrapper in the future. Signed-off-by: Kai Fricke <[email protected]> Signed-off-by: Jack He <[email protected]>
Why are these changes needed?
Pending acceptance of ray-project/enhancements#27, this PR changes the input API to configure persistent storage paths in Ray AIR and Ray Tune.
In a nutshell:
RunConfig.storage_path
that can be set either to a local dir or a remote path.s3://
, orfile://
that points to a NFS mount). In these cases, data will be first written to a local cache dir on the worker, and then synced to a subdirectory in the storage path designated by<experiment_name>/<trial_name>/
./home/foo/ray_results
). In this mode, trial data is synced to the head node via the object store. We would generally recommend using a remote storage path or shared directory instead.This PR deprecates existing input API arguments, and introduces the new
storage_path
configuration. The changes are fully backwards compatible. This is proven by the fact that this PR only changes very few private API calls in the test suites. All tests and examples are expected to continue to work.In a follow-up PR, tests and examples should be adjusted to use the new API.
Related issue number
Replaces #33306
Checks
git commit -s
) in this PR.scripts/format.sh
to lint the changes in this PR.method in Tune, I've added it in
doc/source/tune/api/
under thecorresponding
.rst
file.