mirror of
https://github.com/vale981/ray
synced 2025-03-10 13:26:39 -04:00
a67c8a0739
Packages are uploaded to the GCS for `runtime_env`. These packages are garbage collected when their refcount becomes zero. The problem is the reference doesn't get incremented until the job starts, which happens after the package is uploaded. It's possible for the package's refcount to go to zero in between the upload and when the job starts, causing the package to be deleted before it's needed by the job. It's likely the cause of https://github.com/ray-project/ray/issues/23423. We can't just increment the refcount at the time of upload, because if the script is killed before the job is started (e.g. via Ctrl-C) then the reference will never be decremented and the package will never be deleted. The solution in this PR is to increment the refcount at the time of upload, but automatically decrement after a configurable timeout (default 30s). This should be enough time for the job to start. When the job starts, it increments the refcount as usual and decrements it when the job finishes or is killed. Co-authored-by: Edward Oakes <ed.nmi.oakes@gmail.com> |
||
|---|---|---|
| .. | ||
| backwards_compatibility_scripts | ||
| subprocess_driver_scripts | ||
| pip_install_test-0.5-py3-none-any.whl | ||
| test_backwards_compatibility.py | ||
| test_cli.py | ||
| test_cli_integration.py | ||
| test_common.py | ||
| test_http_job_server.py | ||
| test_job_manager.py | ||
| test_sdk.py | ||
| test_utils.py | ||