# Marking a node in the subcluster as inactive

**URL:** <https://community.thinlinc.com/t/marking-a-node-in-the-subcluster-as-inactive/790>\
**Category:** Community Support\
**Tags:** ha, tlserver\
**Created:** [30 November 2023 09:10 UTC](https://community.thinlinc.com/t/marking-a-node-in-the-subcluster-as-inactive/790 "2023-11-30T09:10:14Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aman](https://avatars.discourse-cdn.com/v4/letter/a/90ced4/32.png) [@Aman](https://community.thinlinc.com/u/Aman)\
**Post date:** [30 November 2023 09:10 UTC](https://community.thinlinc.com/t/marking-a-node-in-the-subcluster-as-inactive/790/1 "2023-11-30T09:10:14Z")

</div>

Hi,

We have a thinlinc HA setup running in cluster mode with 2 nodes in the cluster

```auto
[/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 ?

---

<div class="post-metadata">

**Author:** ![martin](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/martin/32/41_2.png) [@martin](https://community.thinlinc.com/u/martin)\
**Post date:** [30 November 2023 09:31 UTC](https://community.thinlinc.com/t/marking-a-node-in-the-subcluster-as-inactive/790/2 "2023-11-30T09:31:42Z")

</div>

Hello @Aman,

Yes, this is possible! Simply remove [abc.com](http://abc.com) from the `agents=` configuration on both HA nodes, and restart vsmserver on both. This will keep any already running session on that agent, but prevent new sessions from being created on `abc.com`

See [https://www.cendio.com/resources/docs/tag/config\_cluster.html#stopping-new-session-creation-on-select-agents-in-a-cluster](https://www.cendio.com/resources/docs/tag/config_cluster.html#stopping-new-session-creation-on-select-agents-in-a-cluster)

Kind regards,  
Martin

---

<div class="post-metadata">

**Author:** ![Aman](https://avatars.discourse-cdn.com/v4/letter/a/90ced4/32.png) [@Aman](https://community.thinlinc.com/u/Aman)\
**Post date:** [30 November 2023 11:04 UTC](https://community.thinlinc.com/t/marking-a-node-in-the-subcluster-as-inactive/790/3 "2023-11-30T11:04:59Z")

</div>

Thanks a lot @martin
