Limiting simultaneous connections
If monitoring is enabled (p4 configure set monitor=1
or higher), you can set the server.maxcommands configurable
to limit the number of simultaneous command requests that the service
will attempt to handle.
Ideally, this value should be set low enough to detect a runaway script or denial of service attack before the underlying hardware resources are exhausted, yet high enough to maintain a substantial margin of safety between the typical average number of connections and your site’s peak activity.
If P4LOG is set, the server log contain lines of the
form:
Server is now using nnn active threads.
You can use the server log to determine what levels of activity are
typical for your site. Set server.maxcommands
Too many commands
Starting in 2019.1, if a problem occurs with server.maxcommands
Even if end-users see the TooManyCommands error, a user who is super can still run the following commands:
and a user who is operator, such as the administrator of an edge server, can still run the following commands:
| p4 admin | p4 configure | p4 counter |
| p4 counters | ||
| p4 info | ||
| p4 lockstat | p4 login | |
| p4 logout | p4 logtail | |
| p4 monitor | p4 protect | |
| p4 pull | p4 servers | |
| p4 user |
