NVIDIA-NeMo / NVIDIA-NeMo/Curator
Ray temp directory memory leak
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.8k
- Forks
- 328
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 30
Description
Describe the bug
Ray temp directory memory leak when running tasks multiple times.
Steps/Code to reproduce bug
Run any nemo curator pipeline which uses the ray cluster multiple times. Observe the size of the directory at /tmp/ray
Expected behavior
Size of the temp directory does not keep on increasing.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Run a NeMo Curator pipeline that uses the Ray cluster multiple times and measure /tmp/ray after each run. Trace how Ray temporary directories are created and cleaned up during repeated execution. Done means the directory size no longer grows across repeated pipeline runs, with a regression check for that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100