dask / dask/distributed

The dask-scheduler still starts the dashboard when "--no-dashboard" parameter is set.

Open
#6,301 0 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

version: `2022.5. 0`

Ran `dash-scheduler` with `--no-dashboard`, the following information is displayed:

```
Python-3.8]$ dask-scheduler --no-dashboard --no-show
2022-05-07 14:51:30,836 - distributed.scheduler - INFO - -----------------------------------------------
2022-05-07 14:51:30,840 - distributed.http.proxy - INFO - To route to workers diagnostics web server please install jupyter-server-proxy: python -m pip install jupyter-server-proxy
2022-05-07 14:51:30,844 - distributed.scheduler - INFO - State start
2022-05-07 14:51:30,850 - distributed.scheduler - INFO - -----------------------------------------------
2022-05-07 14:51:30,851 - distributed.scheduler - INFO - Clear task state
2022-05-07 14:51:30,852 - distributed.scheduler - INFO - Scheduler at: tcp://7.216.56.36:8786
2022-05-07 14:51:30,852 - distributed.scheduler - INFO - dashboard at: :8787
```

But dashboard port status is `LISTEN`:

```
Python-3.8]$ netstat -ano | grep 8787
tcp 0 0 0.0.0.0:8787 0.0.0.0:* LISTEN off (0.00/0/0)
tcp 0 0 7.216.56.36:8787 10.40.176.75:63536 ESTABLISHED off (0.00/0/0)
tcp 0 0 7.216.56.36:8787 10.40.176.75:63537 ESTABLISHED off (0.00/0/0)
tcp6 0 0 :::8787 :::* LISTEN off (0.00/0/0)
```

ps.

When running Distributed version 2.11.0, this dashboard port is not listened on, as expected.

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.