Closed yucai closed 2 months ago
@edoakes is java calling python something we still maintain?
@edoakes is java calling python something we still maintain?
It's not in active development but we should fix critical bug fixes such as memory leaks. Would classify this as P1.
Dear @edoakes and @jjyao, we are currently undertaking a POC with Ray that is of critical importance to our company's AI platform strategy. We have encountered this significant blocking issue that is impacting our production application which utilizes Ray.
To address this, we've submitted a pull request with a proposed workaround: https://github.com/ray-project/ray/pull/45729.
We would greatly appreciate it if you could review the PR at your earliest convenience. Your expertise would be invaluable in helping us resolve this issue.
CC: @anyscalesam, @kevin85421
@yucai thanks for the contribution. The PR is merged but I think the memory leak still exists but no longer block you?
@yucai can you confirm here ^ @jjyao
EDIT: Jul '24 > should we downgrade priority for this since it's no longer blocking?
closing - please reopen if still relevant @yucai
What happened + What you expected to happen
Reproduction steps:
Expected Behavior: The memory usage should remain stable over time, without significant increases that lead to disk spilling.
Actual Behavior: Continuous increase in object memory usage is observed when the remote Python function do_test is called, eventually leading to spill to disk.
Versions / Dependencies
Ray: 2.9.0
Reproduction script
Issue Severity
High: It blocks me from completing my task.