# Parameters in /subclusters/

In this section, we will describe all the parameters used for defining subclusters. For more information about subclusters see Subclusters. These configuration parameters reside in `/opt/thinlinc/etc/conf.d/cluster.hconf`.

/subclusters/<name>/agents

  All ThinLinc agents part of this ThinLinc subcluster. New user sessions for this subcluster are created on the agents in this list. Agents later removed from the list will continue to function normally for existing sessions until those sessions end. This should be a space-separated list of DNS host names. These will be used for communication between the master and the agent. The name reported to the client is fetched from the agent itself; names in `/subclusters/<name>/agents` are not reported directly to the clients.

/subclusters/<name>/users

  All users who should be associated with this specific ThinLinc subcluster. This should be a space-separated list of usernames. If both `/subclusters/<name>/users` and `/subclusters/<name>/groups` are empty it means the subcluster is a default subcluster.

/subclusters/<name>/groups

  All user groups that should be associated with this specific ThinLinc subcluster. This should be a space-separated list of group names. If both `/subclusters/<name>/groups` and `/subclusters/<name>/users` are empty it means the subcluster is a default subcluster.

/subclusters/<name>/max_users_per_agent

  Maximum concurrent users allowed per agent within the subcluster. The default value is 0, which implies an unlimited number of users. When the limit is reached, the agent will no longer be considered by the load balancer for new users.