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
Sorry for the late response. Just got back from holidays. We test this on Anyscale and it is supposed on a remote cluster. Can you give me your versions for Ray and Fugue?
Hey, no problem. I worked around the issue, so it was ultimately not a blocker for me.
fugue: 0.8.6
ray: 2.9.0
I think the issue might be that ray data does not support ray client. Ray data seems to be used in the Dataframe example. (See here for more details: ray-project/ray#41333 (comment))
As noted, this is separate from #41333 because that is only a workaround to address the fact that rat data does not support using an already connected client without wrapping your actor in a task. This issue is asking for tay client support, not asking for a workaround in its absence. Under the hood, ray data just uses cached RemoteFunction objects (IE what the @ray.remote decorator creates). The only real difference I see is they are invoking remote directly instead of using decorators. Is there no way to configure ray data to connect to an existing cluster's head node without scheduling it as a task through the client (essentially wrapping it in another RemoteFunction)?
When running the "ray" example as provided here, the example fails, if a remote cluster is used.
This ray issue seems related: ray-project/ray#41333
Repro-steps:
It would be nice, if this is documented somewhere (or is there a fix for that?)
Error:
The text was updated successfully, but these errors were encountered: