Josef,
for us, we put a load balancer in front of the login nodes with session
affinity enabled. This makes them land on the same backend node each time.
Also, for interactive X sessions, users start a desktop session on the
node and then use vnc to connect there. This accommodates disconnection
for any reason even for X-based apps.
Personally, I don't care much for interactive sessions in HPC, but there
is a large body that only knows how to do things that way, so it is there.
Brian Andrus
On 2/26/2024 12:27 AM, Josef Dvoracek via slurm-users wrote:
What is the recommended way to run longer interactive job at your
systems?
Our how-to includes starting screen at front-end node and running srun
with bash/zsh inside,
but that indeed brings dependency between login node (with screen) and
the compute node job.
On systems with multiple front-ends users need to remember the login
node where they have their screen session..
Are you anybody using something more advanced and still understandable
by casual user of HPC?
(I know Open On Demand, but often the use of native console has
certain benefits. )
cheers
josef
--
slurm-users mailing list -- slurm-users@lists.schedmd.com
To unsubscribe send an email to slurm-users-le...@lists.schedmd.com
