Skip to content

Commit ae442c8

Browse files
ichernevclintongormley
authored andcommitted
1 parent d9b2047 commit ae442c8

File tree

1 file changed

+8
-6
lines changed

1 file changed

+8
-6
lines changed

520_Post_Deployment/40_rolling_restart.asciidoc

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ The procedure is as follows:
2424
help speed up recovery time
2525

2626
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
2828
short, this is a good idea. You can disable allocation with:
2929
+
3030
[source,js]
@@ -47,8 +47,7 @@ POST /_cluster/nodes/_local/_shutdown
4747

4848
4. Perform maintenance/upgrade
4949
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:
5251
+
5352
[source,js]
5453
----
@@ -60,7 +59,10 @@ PUT /_cluster/settings
6059
}
6160
----
6261
+
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.
6668

0 commit comments

Comments
 (0)