-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
[train+tune][doc] Remove docs sections recommending RAY_AIR_LOCAL_CACHE_DIR
#44284
Conversation
Signed-off-by: Justin Yu <[email protected]>
Signed-off-by: Justin Yu <[email protected]>
Signed-off-by: Justin Yu <[email protected]>
Prior to 2.10, the ``RAY_AIR_LOCAL_CACHE_DIR`` environment variable was the way to configure | ||
the local staging directory to be outside of the home directory (``~/ray_results``). | ||
|
||
``RunConfig(local_dir)`` was another deprecated alternative to set the local staging directory. | ||
|
||
These options are now deprecated, and you should instead set ``storage_path``. | ||
When ``storage_path`` is set, there will no longer be any files written to | ||
``~/ray_results`` starting from Ray 2.10. |
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.
This is a bit confusing since there's a bunch of branching logic based on env var / storage path. Could we maybe simplify this to just focus on the staging directory being set by RAY_AIR_LOCAL_CACHE_DIR
or local_dir
? And not talk about storage_path
?
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.
I kept the mention about switching to storage path as a migration path, because users were setting ONLY the environment variable. But now that the env variable doesn't do anything, they need to switch to setting storage path.
Signed-off-by: Justin Yu <[email protected]>
…CHE_DIR` (ray-project#44284) Removes docs that recommend using the `RAY_AIR_LOCAL_CACHE_DIR` env variable. --------- Signed-off-by: Justin Yu <[email protected]>
…CHE_DIR` (#44284) (#44422) This is a docs only cherry-pick of #44284 Removes docs that recommend using the `RAY_AIR_LOCAL_CACHE_DIR` env variable. --------- Signed-off-by: Justin Yu <[email protected]> Co-authored-by: Kevin H. Luu <[email protected]>
…CHE_DIR` (ray-project#44284) Removes docs that recommend using the `RAY_AIR_LOCAL_CACHE_DIR` env variable. --------- Signed-off-by: Justin Yu <[email protected]>
Why are these changes needed?
The recent local directory refactor (#43369, #43403, #43689) removed usage of the environment variable
RAY_AIR_LOCAL_CACHE_DIR
for configuring the local staging dir.The local staging directory is now a subdirectory of the Ray temp session dir (
/tmp/ray/session_*
), and the customization of this directory location is now offloaded to Ray Core (ray.init(_temp_dir="/tmp/custom")
).This PR updates docs to reflect this new behavior.
Related issue number
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.