question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Proposed additions to `dask-ssh` CLI

See original GitHub issue

I’ve been using dask-ssh the last few days and it has been super helpful. Thanks!

I’ve run into two small things that I think might be of benefit to others to add but wanted to check in (especially given what looks like an upcoming switchover to asyncssh).

  1. dask-ssh keeps an SSH connection open while the scheduler and clients are running – killing the process also shuts down the remote workers (this seems good). However, SSH timeouts also cause this to break and fall over. paramiko (which is currently driving the show here) can send some noise over the wire to keep the connection “active”. This could be an optional way (given some --keepalive flag) to work around timeouts. Might also be a bit of scope creep, but I thought I’d raise it.

  2. Add an option to disable StrictHostKeyChecking – shouldn’t be the default, but if you’ve just spun up resources to add to a cluster, you might not worry so much about having those machines in known_hosts.

Let me know if either/both of these are of interest and I’m happy to take them on.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:9 (9 by maintainers)

github_iconTop GitHub Comments

1reaction
mrocklincommented, Sep 26, 2019

Hi @gforsyth ! I’m very glad to see that you’re engaging with Dask and SSH.

One of the biggest surprises of our user survey was that SSH is the most common deployment strategy, so improvements here likely have high impact.

Have you tried the solution in distributed.deploy.ssh2 ? This new implementation isn’t as battle-tested as the one that you’re currently using, but I think that it’s probably easier to manipulate. It just passes most things through to asyncssh and the workers.

https://github.com/dask/distributed/blob/f7f6bd77ab8d28d8811b94aa84528d3a470f1ff1/distributed/deploy/ssh2.py#L193-L213

Read more comments on GitHub >

github_iconTop Results From Across the Web

SSH - Dask documentation
It is easy to set up Dask on informally managed networks of machines using SSH. This can be done manually using SSH and...
Read more >
Command Line - Dask documentation
There are various mechanisms to deploy these executables on a cluster, ranging from manually SSH-ing into all of the machines to more automated...
Read more >
Command Line Interface - Dask documentation
Dask's CLI is designed to be extensible allowing other projects in the Dask ecosystem (such as distributed ) to add subcommands.
Read more >
Dask Deployment Updates
We've rewritten Dask-Jobqueue for SLURM/PBS/LSF/SGE cluster managers typically found in HPC centers and Dask-Kubernetes. These now share a ...
Read more >
Customize initialization - Dask documentation
To support additional configuration, a single --preload module may register additional command-line arguments by exposing dask_setup as a Click command. This ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found