dask / dask/distributed

Dashboard cannot proxy Worker Dashboards in distributed cluster

Open
#3,846 11 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
1.7k
Forks
778
Avg merge
2h 50m
Merged PRs (30d)
3

Description

**What happened**:

Set up a distributed Dask cluster (1 scheduler and 4 workers) each running on different hosts and accessed the dashboard:

![Screenshot 2020-06-01 at 17 42 17](https://user-images.githubusercontent.com/2104864/83499096-bbcc0500-a4b4-11ea-85e6-fd1b8a96329b.png)

Then tried to access the Worker Dashboards via the Info tab and received the following error:

![Screenshot 2020-06-02 at 09 44 37](https://user-images.githubusercontent.com/2104864/83499750-bae7a300-a4b5-11ea-8a97-a187b3cc77a6.png)

**What you expected to happen**:

Expected to be able to access the worker dashboards successfully

**Anything else we need to know?**:

On initial attempt I got a different error advising that I needed to install the additional `jupyter-sever-proxy` package to enable worker dashboard proxying. However once installed you get the above error because the `jupyter-server-proxy` package enforces a whitelist that only has `localhost` and `127.0.0.1` in it by default.

There does not appear to be any way for users to customise this whitelist so it is hard to see how this feature is ever expected to work except for a fully local cluster i.e. all workers on same physical machine as the scheduler.

Ideally the Dask scheduler dashboard should automatically update the proxy whitelist whenever a new worker is registered.

**Environment**:

- Dask version: 2.17.0
- Python version: 3.8
- Operating System: OS X
- Install method: conda

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.