You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when scheduling Actors or Tasks with memory resource specified i'm expecting that they will be allocated based on memory available on the node for use as private process heap.
This is problematic in the following scenario in Ray Data:
I'm configuring region of node memory to be dedicated for the Object Store (say 35%)
Remainder of the memory i want to be split b/w Tasks/Actors based on their corresponding memory allocation.
Instead i observed that we schedule based on the total available memory that also includes the Object Store.
Versions / Dependencies
2.41
Reproduction script
See above
Issue Severity
Medium: It is a significant difficulty but I can work around it.
The text was updated successfully, but these errors were encountered:
alexeykudinkin
added
bug
Something that is supposed to be working; but isn't
triage
Needs triage (eg: priority, bug/not-bug, and owning component)
core
Issues that should be addressed in Ray Core
labels
Dec 18, 2024
Here's an example of this kind of allocation where 2 actors that aren't supposed to fit on the same node are scheduled onto one:
ruisearch42
added
P1
Issue that should be fixed within a few weeks
and removed
triage
Needs triage (eg: priority, bug/not-bug, and owning component)
labels
Dec 23, 2024
What happened + What you expected to happen
Currently, when scheduling Actors or Tasks with
memory
resource specified i'm expecting that they will be allocated based on memory available on the node for use as private process heap.This is problematic in the following scenario in Ray Data:
Instead i observed that we schedule based on the total available memory that also includes the Object Store.
Versions / Dependencies
2.41
Reproduction script
See above
Issue Severity
Medium: It is a significant difficulty but I can work around it.
The text was updated successfully, but these errors were encountered: