Bokeh service does not start when using processes=False
See original GitHub issueThe bokeh service does not start on Debian when using processes=False
. Strangely, it does start on macOS.
Minimal reproducing example:
from distributed import LocalCluster, Client
cluster = LocalCluster(processes=False)
client = Client(cluster)
print(client.scheduler_info()))
client.close()
On macOS with distributed 1.22.0, the output is:
{
"type": "Scheduler",
"id": "Scheduler-275f860b-d0cd-46a8-865a-c75b8ebd6fc8",
"address": "inproc://10.40.36.245/56255/1",
"services": {
"bokeh": 8787
},
"workers": {
"inproc://10.40.36.245/56255/2": {
"name": "inproc://10.40.36.245/56255/2",
"memory_limit": 17179869184,
"host": "10.40.36.245",
"resources": {},
"ncores": 8,
"services": {
"bokeh": 61024
},
"local_directory": "/Users/laurent/[...]/dask-worker-space/worker-bh9f2yjh",
"pid": 56255,
"cpu": 0,
"memory": 100495360,
"time": 1.53373248E9,
"read_bytes": 0,
"write_bytes": 0,
"num_fds": 68
}
}
}
While running the same code on Debian (in a Docker container with no other processes running) results in the below output. Notice that on Debian, the "services"
value is an empty dict! With processes=True
, the bokeh service does start.
{
"type": "Scheduler",
"id": "Scheduler-fd83c67d-515a-499f-9c1c-fd9641d54d51",
"address": "inproc://172.18.0.2/104/1",
"services": {},
"workers": {
"inproc://172.18.0.2/104/2": {
"name": "inproc://172.18.0.2/104/2",
"memory_limit": 12575559680,
"host": "172.18.0.2",
"resources": {},
"ncores": 6,
"services": {
"bokeh": 41839
},
"local_directory": "/[...]/dask-worker-space/worker-0yv06g56",
"pid": 104,
"cpu": 0,
"memory": 112869376,
"time": 1.53373286E9,
"read_bytes": 0,
"write_bytes": 0,
"num_fds": 24
}
}
}
Issue Analytics
- State:
- Created 5 years ago
- Reactions:6
- Comments:13 (6 by maintainers)
Top Results From Across the Web
Dask dashboard not starting when starting scheduler with api
Since bokeh is installed, I'd expect the dashboard to be started. When I start the scheduler using the command line however, the dashboard ......
Read more >bokeh-server does not start - Community Support
The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error...
Read more >Python API - Dask documentation
You can create a dask.distributed scheduler by importing and creating a Client with no arguments. This overrides whatever default was previously set.
Read more >Deploying Bokeh Apps — HoloViews v1.15.3
Unfortunately, a static approach like this cannot support any HoloViews object ... To start a Bokeh server directly from a notebook we can...
Read more >Deploying a Web App with Bokeh Tutorial - DataCamp
Hence, you don't need to have prior knowledge of JavaScript to create an app! The following image provides a summary of how the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
add the ‘ip’ params, e.g. client = Client(processes=False, threads_per_worker=4,ip=‘127.0.0.1’,n_workers=1, memory_limit=‘2GB’)
Same problem here on a Windows 10, with dask, dask.distributed and bokeh installed: Setting processes=False on Client or LocalCluster, creates this ‘inproc’ unreachable endpoint.
I tried setting the ip as suggested by @weiweiWYW but there is no apparent ip parameter in the Dask.distributed Client API. Simply passing the address parameter to the Client,
Raises a NotImplementedError at asyncio/events.py