ValueError: After taking into account object store and redis memory usage, the amount of memory on this node available for tasks and actors (-0.01 GB) is less than 0% of total. You can adjust these settings with ray.init(memory=<bytes>, object store memory=<bytes>
See original GitHub issueWhat is the problem?
when i run ray in ML platform,
ValueError: After taking into account object store and redis memory usage, the amount of memory on this node available for tasks and actors (-0.01 GB) is less than 0% of total. You can adjust these settings with ray.init(memory=<bytes>, object store memory=<bytes>
occurs can you tell me the approximate value of memory size /object store memory i should set ? thanks
Ray version and other system information (Python version, TensorFlow version, OS):
Reproduction (REQUIRED)
Please provide a script that can be run to reproduce the issue. The script should have no external library dependencies (i.e., use fake or mock data / environments):
If we cannot run your script, we cannot fix your issue.
- I have verified my script runs in a clean environment and reproduces the issue.
- I have verified the issue also occurs with the latest wheels.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:21 (10 by maintainers)
Top Results From Across the Web
RayOutOfMemoryError: More than 95% of the memory is used
High: It blocks me to complete my task. I am new to ray and trying to run an open source code at yuta0821/agent57_pytorch....
Read more >Failure to deploy ray actor to flask app on heroku
ValueError : After taking into account object store and redis memory usage, the amount of memory on this node available for tasks and...
Read more >A brand new website interface for an even better experience!
ValueError : After taking into account object store and redis memory usage, ... this node available for tasks and actors (-0.01 GB) is...
Read more >The Ray API — Ray 0.01 documentation - Read the Docs
init and shut them down when the script exits. These processes include local and global schedulers, an object store and an object manager,...
Read more >Amazon MemoryDB for Redis Pricing
You are charged based on three components: on-demand instance hours per node, volume of data written to your cluster, and snapshot storage that...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

After upgrading to Ray 2.0, issue is gone on my side.
When you don’t specify the object store memory, it uses 20% of available memory. I think your machine doesn’t have enough available memory (20% of available memory is even less than 80MB).
You can manually specify object_store_memory to avoid this.
the minimal you should specify is
78643200.Better solution is to use an instance that has more available memory.