Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dask dashboard not showing workers after cluster.stop_workers(cluster.jobs) #28

Closed
apatlpo opened this issue Apr 4, 2018 · 5 comments
Closed

Comments

@apatlpo
Copy link

apatlpo commented Apr 4, 2018

On PBS with dask-jobqueue #25
If I start a cluster, kill workers with cluster.stop_workers(cluster.jobs) and try to restart a new cluster, then workers do not show up in the dashboard.
Is it expected behavior?
Could we do something about this?

@apatlpo
Copy link
Author

apatlpo commented Apr 4, 2018

I should also mention that the new set of worker seem to be working correctly

@guillaumeeb
Copy link
Member

@apatlpo can you describe precisely the commands you are launching? Are you using cluster.restart()?

If so, I imagine it is failing because we do not update worker launching command to point to the new scheduler address (scheduler port is probably changing on restart).

But you could achieve something similar by only launching cluster.start_worker(n) or cluster.scale_up.

@mrocklin
Copy link
Member

mrocklin commented Apr 4, 2018 via email

@guillaumeeb
Copy link
Member

Obviously you are right @mrocklin. We'll wait for @apatlpo to clarify.

@apatlpo
Copy link
Author

apatlpo commented Apr 5, 2018

I believe this was just noise on my part, deeply sorry.

It works fine today with:


cluster.stop_workers(cluster.jobs)

and then:

cluster.start_workers(4)

Even client.restart() and client.upload_file() are working.

I have other issues (workers dying) but these will motivate other posts.

Sorry again

@apatlpo apatlpo closed this as completed Apr 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants