Chen Shen
Chen Shen
That seems a lot of data. Can you try run `ray memory --stats-only` to see the object store memory usage?
end up picked https://github.com/ray-project/ray/pull/27567 which should solve this problem
Do we know why the node crashed?
Yeah we can unblock the release for now and look into it in 2.1
Will not cherry pick this into 2.0
don't need to be picked to release branch i guess?
@kira-lin do I understand correctly that this only applies to stateless actors? Also it will be nice to add unit test/integration test to show the problem it solves.
Do we need cherry pick this to 2.0.0 release branch?
hmm this (setting upper bound) has been the practical strategy we have been following for grpcio right (and[ other core dependencies](https://github.com/ray-project/ray/blob/master/python/requirements.txt#L23))? Empirically, for grpcio, not setting upper bound has caused...
- not all ray dependency has the same impact radius. grpcio is a critical dependency for ray and ray core. i.e. if it breaks ray won't work, AT ALL. -...