Tips & Tricks

Node Specific Client Session Limit


This quick tip shows how to limit client sessions on a specific node.

This functionality appears to have been introduced in 7.1, possibly earlier, however the previous version’s documentation doesn’t mention this.

The general way to set client sessions is using the SET_CONFIG_PARAMETER function along with the MaxClientSessions parameter. The default value at the database level is 50. This is parameter is used to increase the number of active client sessions or when stopping the database.

If there’s a need to prevent clients from connecting to a particular node, the node can be added with the function:

Before the change, configuration_parameters looks like:

After the change, configuration_parameters looks like:

To clear the change, the node name must be used passed with a null value:


About the author / 

Norbert Krupa

Norbert is the founder of and a Solutions Engineer at Talend. He is an HP Accredited Solutions Expert for Vertica Big Data Solutions. He has written the Vertica Diagnostic Queries which aim to cover monitoring, diagnostics and performance tuning. The views, opinions, and thoughts expressed here do not represent those of the user's employer.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Upcoming Events

  • No upcoming events
AEC v1.0.4

Subscribe to Blog via Email

Enter your email address to subscribe and receive notifications of new posts by email.

Read more use cases here.


This site is not affiliated, endorsed or associated with HPE Vertica. This site makes no claims on ownership of trademark rights. The author contributions on this site are licensed under CC BY-SA 3.0 with attribution required.
%d bloggers like this: