Closed tjcrone closed 4 years ago
I get the same type of error when trying to create a new cluster using the Dask labextension. Here are some details on my configuration:
dask.config.config['gateway']
{'auth': {'type': 'jupyterhub', 'kwargs': {}},
'cluster': {'options': {'image': '{JUPYTER_IMAGE_SPEC}'}},
'public_address': '/services/dask-gateway/',
'address': 'http://10.1.128.135:8000/services/dask-gateway/',
'proxy_address': 'gateway://traefik-ooi-prod-dask-gateway.ooi-prod:80',
'http-client': {'proxy': True}}
Any logs from your dask-gateway pods (controller, api, and traefik) or the scheduler pod?
I rolled back Helm and restarted all the pods and things seem to be sorted now. At least, I can connect to a Dask cluster. There seems to still be a lot of strangeness. Grafana and other resources installed that I thought we disabled. I wonder if there is any way for us to move toward having a deployment that doesn't change all the time? Something like pangeo-stable and then pangeo-dev? I wonder if that could help things?
Hard to say when we aren't sure what changed / caused the trouble.
IIRC, Sebastian has been working on doing independent deployments. I'm not sure what the status is on that.
On Wed, Oct 21, 2020 at 10:06 AM Tim Crone notifications@github.com wrote:
I rolled back Helm and restarted all the pods and things seem to be sorted now. At least, I can connect to a Dask cluster. There seems to still be a lot of strangeness. Grafana and other resources installed that I thought we disabled. I wonder if there is any way for us to move toward having a deployment that doesn't change all the time? Something like pangeo-stable and then pangeo-dev? I wonder if that could help things?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/pangeo-data/pangeo-cloud-federation/issues/792#issuecomment-713644671, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKAOITIOMKPD3KZTMINHY3SL32HPANCNFSM4SZWQTNQ .
Okay that would be great! I will close this for now since I think the original issue is solved. Thanks for your help.
When I try to start a new Dask cluster from inside a notebook:
I get a Cluster not found error:
However the scheduler
dask-scheduler-94433c9e4d69409eaf0acbf438ffc9d4
has been started.Any thoughts on what might be going on here?