You are currently browsing legacy 5.0 version of documentation. Click here to switch to the newest 5.1 version.
Client Configuration (Per Database)
- The general server Client Configuration can be overwritten per database.
Client Requests Configuration - Per Database
Specific Client Configuration Per Database
1. Identity parts separator
Changes the default separator for automatically generated document IDs.
You can use any
2. Max number of requests per session
Set this number to restrict the number of requests (Reads & Writes) per session in the client API.
Default value: 30
3. Use Session Context for Load Balancing
Allow client sessions to select their topology by tag, so they'd be able to load-balance their requests.
Optionally, select a hash seed to randomize the topology that clients would use.
4. Read balance behavior
Set the load-balance method that the client will use when accessing a node with Read requests.
The method selected will also affect the client's decision of which node to failover to in case of issues with the Read request.
Note: Write requests will always access the preferred node calculated by the client.
Available options are:
- Round Robin
- Fastest Node
For a detailed explanation about each option see: Read Balance Behavior Options
This view will be as in the above image when a general configuration is defined.
If a general configuration is not yet defined then this view will be similar to the general server configuration view.