Hi,
We have a thinlinc HA setup running in cluster mode with 2 nodes in the cluster
[/vsmserver/subclusters/default]
agents=abc.com def.com
[/vsmserver/HA]
# Enable HA operations by setting this to 1.
enabled=1
# A space-separated list of the nodes in the cluster
nodes=abc.com def.com
Now, we have a scheduled reboot of one node abc.com
in the coming days. So, what I wanted is that from now till the day of reboot all the sessions get created in another node i.e def.com
.
Normally you’d mark one server (thats up for a reboot) for “out-of-service” - so existing sessions on it gets time to finish - but no new ones are started. Does Thinlinc support that? (it’s like you do with slurm, and kubernetes nodes)
Is this possible and how ? that too without affecting my running sessions on abc.com
node ?