KubeCluster creation is hanging on in Jupyter about dask-kubernetes HOT 6 CLOSED

On Mon, Oct 1, 2018 at 10:56 AM Guillaume Eynard-Bontemps < ***@***.***> wrote: OK, so sorry for the really newbie issue here. I've just deployed a Pangeo style cluster on GCE, and I am trying to start a KubeCluster as in the Pangeo provided example, for instance *dask-array.ipynb*. But no luck for the moment, the notebook cell is just displayed as running but nothing happens. Should I give more argument thant just from dask_kubernetes import KubeCluster cluster = KubeCluster(n_workers=10) cluster like a pod_spec for instance? I'm not sure how this is suppose to work (or how it works on Pangeo?), as in the default config from this repo the pod spec is empty. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#103>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AASszFpsUg1jcVN_MNldn-y6SfZKvejKks5ugi0ygaJpZM4XCP5h> .

On Mon, Oct 1, 2018 at 11:07 AM Guillaume Eynard-Bontemps < ***@***.***> wrote: Still nothing with from dask_kubernetes import KubeCluster cluster = KubeCluster.from_yaml('worker-spec.yml') cluster.scale_up(10) cluster How much time should it take? Should I be able to see something happen on GCE monitoring side? Is there a way to see where it hangs in python? I tried to add debug logs with no luck. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#103 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AASszCW9nwhnwW_t1KIQVuaKPKFSh2B3ks5ugi-wgaJpZM4XCP5h> .

On Mon, Oct 1, 2018 at 11:31 AM Guillaume Eynard-Bontemps < ***@***.***> wrote: Seem like this is not dask-kubernetes related... I'm not even able to compute 2+2 in a cell... Probably more a Pangeo deployment related issue. But I don't see anything relevant in the notebook server logs. I think that the Python kernel did not even start... Sorry for the trouble. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#103 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AASszMhZX4I-TSCR_xVOybn7orqoP6pTks5ugjVEgaJpZM4XCP5h> .