Start/notes.ini Parameters/Server_MaxUsers

Server_MaxUsers

Parameter: Server_MaxUsers
Short description: Maximum number of users allowed to access a server simultaneously. When the value is reached, the server enters the MAXUSERS state and accepts no new Open-Database requests.

Profile

Parameter
Server_MaxUsers
Category
Performance / Memory (workload balancing)
Available since
At least 9.0.1 (HCL documentation)
GUI equivalent
According to HCL, no direct GUI option. Configurable in the Configuration document on the NOTES.INI Settings tab.
Possible values
0 = unlimited; any positive integer = maximum value

Description

According to the HCL product documentation, Server_MaxUsers sets the maximum number of users allowed to access a server simultaneously. When this number is reached, the server changes to the MAXUSERS status and accepts no new Open-Database requests.
Values (verbatim from the HCL docs):
  • 0 — Unlimited access to server by users.
  • number — Restricts number of active users to the number you specify.
According to the HCL help page Setting the maximum number of users on a server (admn_settingthemaximumnumberofusersonaserver_t.html), Server_MaxUsers is particularly suitable for workload balancing in a cluster: when a server reaches its user limit, additional users can shift to other cluster members.
The HCL Customer Support article KB0105972 (How to Optimize Work Load Balancing in your Domino Server) describes this use case in addition.

Example configuration

Server_MaxUsers=500
With Server_MaxUsers=500, the server accepts up to 500 active users and rejects further Open-Database requests. The actually sensible value depends on hardware and load.

Notes & pitfalls

  • When the limit is reached, the server enters the MAXUSERS state — visible in console output and logs.
  • Server_MaxUsers=0 disables the limit (unlimited).
  • In a cluster context, the parameter can be used for workload balancing (see HCL help page Setting the maximum number of users on a server).
  • Related limits: Server_Availability_Threshold triggers failover based on the Server Availability Index (a different, soft mechanism), while Server_MaxUsers acts as a hard cap. Use Server_Restricted to deliberately trigger failover during planned maintenance.
  • According to HCL there is no direct GUI equivalent; the value can be maintained via the NOTES.INI Settings tab of a Configuration document.

Sources (HCL Product Documentation & Customer Support)