You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* You can override the [client-configuration](../../../studio/server/client-configuration.mdx) that is set server-wide __per database__:
19
-
20
-
* From the Studio - as described in this article
21
-
* From the Client API - see [put client-configuration operation](../../../client-api/operations/server-wide/configuration/put-serverwide-client-configuration.mdx#put-client-configuration-(server-wide))
22
-
23
-
* Setting the client-configuration from the studio sets the configuration on the RavenDB server.
24
-
This enables administrators to dynamically control the client behavior even after it has started running.
25
-
e.g. manage load balancing of client requests on the fly in response to changing system demands.
26
-
27
-
</Admonition>
28
-
## Set the client-configuration (for database)
29
-
30
-
31
-
32
-
33
-
**1. Identity parts separator**
34
-
35
-
* Changes the default **separator** for automatically generated document IDs.
36
-
You can use any `char` except `|` (pipe).
37
-
Default value: `/`
38
-
39
-
**2. Max number of requests per session**
40
-
41
-
* Set this number to restrict the number of requests (***Reads*** & ***Writes***) per session in the client API.
42
-
Default value: 30
43
-
44
-
**3. Use Session Context for Load Balancing**
45
-
46
-
* Allow client sessions to select their topology by tag,
47
-
so they'd be able to load-balance their requests.
48
-
49
-
* Optionally, select a hash seed to randomize the topology that clients would use.
50
-
51
-
* For a detailed explanation see: [Load Balance Behavior](../../../client-api/configuration/load-balance/load-balance-behavior.mdx).
52
-
53
-
**4. Read balance behavior**
54
-
55
-
* Set the load-balance method that the client will use when accessing a node with ***Read*** requests.
56
-
The method selected will also affect the client's decision of which node to failover to in case of issues with the ***Read*** request.
57
-
Note: ***Write*** requests will always access the [preferred node](../../../client-api/configuration/load-balance/overview.mdx#the-preferred-node) calculated by the client.
58
-
59
-
* Available options are:
60
-
*_None_
61
-
*_Round Robin_
62
-
*_Fastest Node_
63
-
64
-
* For a detailed explanation see: [Read Balance Behavior](../../../client-api/configuration/load-balance/read-balance-behavior.mdx).
This view will be as in the above image when the general server [Client Configuration](../../../studio/server/client-configuration.mdx) is not yet defined.
71
-
If a general server client-configuration is defined then this view will show the __effective configuration__ for the specific database.
72
-
19
+
* You can **override** the [server-wide client configuration](../../../studio/server/client-configuration.mdx) per database:
20
+
You can do this using:
21
+
* The Studio - as described in this article
22
+
* The Client API - see [Put client configuration operation](../../../client-api/operations/maintenance/configuration/put-client-configuration.mdx)
23
+
24
+
* When set from the Studio, the client configuration is stored directly on the RavenDB server
25
+
and applies to any client that connects to the specific database.
26
+
27
+
* These settings override the client's own configuration,
28
+
which can be set in your application code when initializing the _DocumentStore_.
29
+
This enables administrators to dynamically control client behavior, even after the client has started running.
30
+
For example, adjusting load balancing behavior on the fly in response to changing system demands.
31
+
32
+
* In this article:
33
+
*[Set the client configuration (for database)](../../../studio/database/settings/client-configuration-per-database.mdx#set-the-client-configuration-for-database)
34
+
73
35
</Admonition>
74
36
37
+
<Panelheading="Set the client configuration (for database)">
38
+
39
+
40
+
41
+
1. Go to **Settings > Client Configuration**
42
+
43
+
2. Select whether to override the server-wide client configuration:
44
+
Toggle **"Use server config"** to make this database use the settings defined [server-wide](../../../studio/server/client-configuration.mdx).
45
+
Toggle **"Use database config"** to override the server-wide settings with a configuration specific to this database.
46
+
47
+
3.**Identity parts separator**
48
+
Set the **separator character** used in automatically generated document IDs of type **identity** and **HiLo**.
49
+
It applies only to [Identity IDs](../../../server/kb/document-identifier-generation.mdx#strategy-identity) generated by the server
50
+
and [HiLo IDs](../../../server/kb/document-identifier-generation/#strategy-hilo-algorithm) generated by the client.
51
+
You can use any single character except `|` (pipe).
52
+
Default value: `/`
53
+
54
+
4.**Maximum number of requests per session**
55
+
Set this number to restrict the number of requests (***Reads*** & ***Writes***) allowed per session when using the Client API.
56
+
Default value: `30`
57
+
58
+
5.**Load balance behavior**
59
+
Set the Load balance method for ***Read*** & ***Write*** requests.
60
+
For a detailed explanation see: [Load balance behavior](../../../client-api/configuration/load-balance/load-balance-behavior.mdx).
* Set the client-configuration for __all__ databases in the cluster:
19
-
20
-
* From the Studio - as described in this article
21
-
22
-
* From the Client API - see [put client-configuration operation](../../client-api/operations/server-wide/configuration/put-serverwide-client-configuration.mdx)
23
-
24
-
* These default values can be overwritten __per database__ in [client-configuration (for database)](../../studio/database/settings/client-configuration-per-database.mdx)
25
-
26
-
* Setting the client-configuration from the studio sets the configuration on the RavenDB server.
27
-
This enables administrators to dynamically control the client behavior even after it has started running.
28
-
e.g. manage load balancing of client requests on the fly in response to changing system demands.
19
+
* The client configuration can be set for **ALL** databases in the cluster.
20
+
You can do this using:
21
+
* The Studio - as described in this article
22
+
* The Client API - see [Put client configuration operation](../../client-api/operations/server-wide/configuration/put-serverwide-client-configuration.mdx)
23
+
24
+
* When set from the Studio, the client configuration is stored directly on the RavenDB server
25
+
and applies to any client that connects to any database in the cluster.
26
+
27
+
* These settings override the client's own configuration,
28
+
which can be set in your application code when initializing the _DocumentStore_.
29
+
This enables administrators to dynamically control client behavior, even after the client has started running.
30
+
For example, adjusting load balancing behavior on the fly in response to changing system demands.
31
+
32
+
* To override these global values and define a separate client configuration for a specific database,
* Changes the default **separator** for automatically generated document IDs.
38
-
You can use any `char` except `|` (pipe).
39
-
Default value: `/`
40
-
41
-
**2. Max number of requests per session**
42
-
43
-
* Set this number to restrict the number of requests (***Reads*** & ***Writes***) per session in the client API.
44
-
Default value: 30
45
-
46
-
**3. Use Session Context for Load Balancing**
47
-
48
-
* Allow client sessions to select their topology by tag,
49
-
so they'd be able to load-balance their requests.
50
-
51
-
* Optionally, select a hash seed to fix the topology that clients would use.
52
-
53
-
* For a detailed explanation see: [Load Balance Behavior](../../client-api/configuration/load-balance/load-balance-behavior.mdx).
54
-
55
-
**4. Read balance behavior**
56
-
57
-
* Set the load-balance method that the client will use when accessing a node with ***Read*** requests.
58
-
The method selected will also affect the client's decision of which node to failover to in case of issues with the ***Read*** request.
59
-
Note: ***Write*** requests will always access the [preferred node](../../client-api/configuration/load-balance/overview.mdx#the-preferred-node) calculated by the client.
60
-
61
-
* Available options are:
62
-
*_None_
63
-
*_Round Robin_
64
-
*_Fastest Node_
65
-
66
-
* For a detailed explanation about each option see: [Read Balance Behavior](../../client-api/configuration/load-balance/read-balance-behavior.mdx).
67
-
68
-
69
39
40
+
<Panelheading="Set the client configuration (server-wide)">
0 commit comments