[Serve] Validate `object_store_memory` in ray_actor_options error about ray HOT 7 CLOSED

Q: Did you set object_store_memory to a float?
A: Yes, as you can see from the the reproduction script:

 @serve.deployment(ray_actor_options={"object_store_memory": 20 * 1024 * 1024})

I think this line of code is the reason that cause the bug, which convert the value of object_store_memory to float, I think change it from object_store_memory: float to object_store_memory: int will fix this bug.

from ray.

I think this bug is caused by this line of code, after I change the value from _counting_option("object_store_memory", False) to _resource_option("object_store_memory") the error fixed.

from ray.

@aRyBernAlTEglOTRO did you set object_store_memory to a float? Or did you set it to an int and then see this error?

It looks like this option is expected to be an int instead of a float (code link). If Serve is converting it to a float, then that sounds like a bug.

from ray.

It turns out object_store_memory is not supported in Ray Core (see issue). I'm reopening this issue until we decide how to handle it in Ray Serve.

from ray.

@aRyBernAlTEglOTRO We're planning to remove object_store_memory in Ray Serve. The option is not supported in Ray Core, so setting it is a no-op in Serve. Could you explain your use case for object_store_memory, so we can see if there's another way to accomplish it?

from ray.

@shrekris-anyscale Thank you for your effort. The reason that I use object_store_memory is due to that I met some memory leak issue when I used Ray Serve. Therefore I searched around for some parameters which can control the memory usage of deployment, at that time I encontered the object_store_memory, but even after I set this parameter, the memory leak issue still exist.

from ray.

Can you file a separate issue for the memory leak? Do you know if it's happening in the Ray Serve code, or the application code?

from ray.