client.cluster == None when Client() instantiated with scheduler address

[mturok]

Hi,

It seems that client.cluster isn't populated when Client() is instantiated with a scheduler address and not a cluster object.

Is there a way to get a handle to the cluster itself from the scheduler in a clean way?

(This is really related to other issues about being able to cleanly shut down a cluster from a client: #1085)

Michael

[mrocklin]

Short answer is no. Cluster objects are not strictly required to use Dask, nor are they guaranteed to exist on the same machine. In principle the client only ever talks to the scheduler. I suspect that you may be interested in #2235

…

On Fri, Sep 21, 2018 at 2:11 PM, Michael Turok ***@***.***> wrote: Hi, It seems that client.cluster isn't populated when Client() is instantiated with a scheduler address and not a cluster object. Is there a way to get a handle to the cluster itself from the scheduler in a clean way? (This is really related to other issues about being able to cleanly shut down a cluster from a client: #1085 <#1085>) Michael — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2266>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AASszHDlZy955tm6gbqbrNadaEgDFynyks5udSvdgaJpZM4W0ovk> .