Detecting a resource deadlock

How severe does this issue affect your experience of using Ray?

  • None: Just asking a question out of curiosity

What’s the best way to detect if a workload on a (statically sized) Ray cluster has hit a deadlock due to insufficient resources?
A programmatic mechanism to check (as opposed to just warning logs) would be ideal.

Currently there is no such programmatic mechanism. The best way for now is checking logs.