8
I'm working on a computing cluster which has several hundreds of nodes. A load-balancing scheme picks an idle node to login to when ssh-ing into the cluster. As a result, it is very unlikely to re-login into a previous machine on subsequent calls to ssh.
However, I would like to use tmux
on the remote to setup a session which persists between different logins.
I'm looking for different options which can be used to achieve the desired behaviour. I came up with the following option, which is, however, not really a "good" solution:
Pick one node and stick to it.
I.e. after being logged into machinenode-XXXX
by the load-balancer open a new ssh connection tonode-0042
and runtmux
there.Using
ssh
'sProxyCommand
this could even be achieved in a seamless manner, i.e. the user typesssh node-0042
which opens a connection the the cluster login and uses this connection as proxy for a connection thenode-0042
.This has the obvious downside that the user does not gain anything from the load-balancing mechanism.
Do you have any advice on how to handle this situation? Any idea for a different approach to solve it (is it possible to "move" a running tmux
server to a different machine [which is a carbon copy of the current machine]?).
How did you proceed? – Herman Toothrot – 2019-03-06T07:53:24.497