@@ -24,7 +24,7 @@ The procedure is as follows:
24
24
help speed up recovery time
25
25
26
26
2. Disable shard allocation. This prevents Elasticsearch from re-balancing
27
- missing shards until you tell it otherwise. If you know the maintenance will be
27
+ missing shards until you tell it otherwise. If you know the maintenance window will be
28
28
short, this is a good idea. You can disable allocation with:
29
29
+
30
30
[source,js]
@@ -47,8 +47,7 @@ POST /_cluster/nodes/_local/_shutdown
47
47
48
48
4. Perform maintenance/upgrade
49
49
5. Restart node, confirm that it joins the cluster
50
- 6. Repeat 3-5 for the rest of your nodes
51
- 7. Re-enable shard allocation using:
50
+ 6. Re-enable shard allocation using:
52
51
+
53
52
[source,js]
54
53
----
@@ -60,7 +59,10 @@ PUT /_cluster/settings
60
59
}
61
60
----
62
61
+
63
- Shard re-balancing may take some time. At this point you are safe to resume
64
- indexing (if you had previously stopped), but waiting until the cluster is fully
65
- balanced before resuming indexing will help speed up the process
62
+ Shard re-balancing may take some time. Wait until the cluster has _green_ status.
63
+
64
+ 7. Repeat 2-6 for the rest of your nodes
65
+ 8. At this point you are safe to resume indexing (if you had previously stopped),
66
+ but waiting until the cluster is fully balanced before resuming indexing will help
67
+ to speed up the process.
66
68
0 commit comments