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
| name || The sentinel identifier for a particular database cluster |
32
-
| sentinelRootNodes || An array of root nodes that are part of the sentinel cluster, which will be used to get the topology. Each element in the array is a client configuration object. There is no need to specify every node in the cluster: 3 should be enough to reliably connect and obtain the sentinel configuration from the server |
33
-
| maxCommandRediscovers |`16`| The maximum number of times a command will retry due to topology changes. |
34
-
| nodeClientOptions || The configuration values for every node in the cluster. Use this for example when specifying an ACL user to connect with |
35
-
| sentinelClientOptions || The configuration values for every sentinel in the cluster. Use this for example when specifying an ACL user to connect with |
36
-
| masterPoolSize |`1`| The number of clients connected to the master node |
37
-
| replicaPoolSize |`0`| The number of clients connected to each replica node. When greater than 0, the client will distribute the load by executing read-only commands (such as `GET`, `GEOSEARCH`, etc.) across all the cluster nodes. |
38
-
| reserveClient |`false`| When `true`, one client will be reserved for the sentinel object. When `false`, the sentinel object will wait for the first available client from the pool. |
| name || The sentinel identifier for a particular database cluster |
32
+
| sentinelRootNodes || An array of root nodes that are part of the sentinel cluster, which will be used to get the topology. Each element in the array is a client configuration object. There is no need to specify every node in the cluster: 3 should be enough to reliably connect and obtain the sentinel configuration from the server |
33
+
| maxCommandRediscovers |`16`| The maximum number of times a command will retry due to topology changes. |
34
+
| nodeClientOptions || The configuration values for every node in the cluster. Use this for example when specifying an ACL user to connect with |
35
+
| sentinelClientOptions || The configuration values for every sentinel in the cluster. Use this for example when specifying an ACL user to connect with |
36
+
| masterPoolSize |`1`| The number of clients connected to the master node |
37
+
| replicaPoolSize |`0`| The number of clients connected to each replica node. When greater than 0, the client will distribute the load by executing read-only commands (such as `GET`, `GEOSEARCH`, etc.) across all the cluster nodes. |
38
+
| scanInterval |`10000`| Interval in milliseconds to periodically scan for changes in the sentinel topology. The client will query the sentinel for changes at this interval. |
39
+
| passthroughClientErrorEvents |`false`| When `true`, error events from client instances inside the sentinel will be propagated to the sentinel instance. This allows handling all client errors through a single error handler on the sentinel instance. |
40
+
| reserveClient |`false`| When `true`, one client will be reserved for the sentinel object. When `false`, the sentinel object will wait for the first available client from the pool. |
41
+
39
42
## PubSub
40
43
41
44
It supports PubSub via the normal mechanisms, including migrating the listeners if the node they are connected to goes down.
@@ -60,7 +63,7 @@ createSentinel({
60
63
});
61
64
```
62
65
63
-
In addition, it also provides the ability have a pool of clients connected to the replica nodes, and to direct all read-only commands to them:
66
+
In addition, it also provides the ability have a pool of clients connected to the replica nodes, and to direct all read-only commands to them:
0 commit comments