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
Copy file name to clipboardExpand all lines: docs/elasticsearch/modules/gateway/index.textile
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ h2. Recovery After Nodes / Time
32
32
33
33
p. In many cases, the actual cluster meta data should only be recovered after specific nodes have started in the cluster, or a timeout has passed. This is handy when restarting the cluster, and each node local index storage still exists to be reused and not recovered from the gateway (which reduces the time it takes to recover from the gateway).
34
34
35
-
p. The @gateway.recover_after_nodes@ setting (which accepts a number) controls after how many nodes within the cluster recovery will start. The @gateway.recovery_after_time@ setting (which accepts a time value) sets the time to wait till recovery happens once the nodes are met.
35
+
p. The @gateway.recover_after_nodes@ setting (which accepts a number) controls after how many nodes within the cluster recovery will start. The @gateway.recover_after_time@ setting (which accepts a time value) sets the time to wait till recovery happens once the nodes are met.
36
36
37
37
p. The @gateway.expected_nodes@ allows to set how many nodes are expected to be in the cluster, and once met, the `recover_after_time` is ignored and recovery starts. For example setting:
0 commit comments