Docs: rolling upgrade process seems incorrect #7973
Assignees
Labels
Comments
|
+1 |
|
Think the step on waiting for the green thing should be stated explicitly in the instructions. |
This was referenced Oct 17, 2014
dadoonet
added a commit
to dadoonet/elasticsearch
that referenced
this issue
Oct 24, 2014
When reading the [rolling upgrade process](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-upgrade.html#rolling-upgrades), you can see that we wrote: * disable allocation * upgrade node1 * upgrade node2 * upgrade node3 * ... * enable allocation That won't work as after a node has been removed and restarted, no shard will be allocated anymore. So closing node2 and remaining nodes, won't help to serve index and search request anymore. We should write: * disable allocation * upgrade node1 * enable allocation * wait for shards being recovered on node1 * disable allocation * upgrade node2 * enable allocation * wait for shards being recovered on node2 * disable allocation * upgrade node3 * enable allocation * wait for shards being recovered on node3 * disable allocation * ... * enable allocation I think this documentation update should go in 1.3, 1.4, 1.x and master branches. Closes elastic#7973.
dadoonet
added a commit
that referenced
this issue
Oct 24, 2014
When reading the [rolling upgrade process](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-upgrade.html#rolling-upgrades), you can see that we wrote: * disable allocation * upgrade node1 * upgrade node2 * upgrade node3 * ... * enable allocation That won't work as after a node has been removed and restarted, no shard will be allocated anymore. So closing node2 and remaining nodes, won't help to serve index and search request anymore. We should write: * disable allocation * upgrade node1 * enable allocation * wait for shards being recovered on node1 * disable allocation * upgrade node2 * enable allocation * wait for shards being recovered on node2 * disable allocation * upgrade node3 * enable allocation * wait for shards being recovered on node3 * disable allocation * ... * enable allocation I think this documentation update should go in 1.3, 1.4, 1.x and master branches. Closes #8218 Closes #7973.
dadoonet
added a commit
that referenced
this issue
Oct 24, 2014
When reading the [rolling upgrade process](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-upgrade.html#rolling-upgrades), you can see that we wrote: * disable allocation * upgrade node1 * upgrade node2 * upgrade node3 * ... * enable allocation That won't work as after a node has been removed and restarted, no shard will be allocated anymore. So closing node2 and remaining nodes, won't help to serve index and search request anymore. We should write: * disable allocation * upgrade node1 * enable allocation * wait for shards being recovered on node1 * disable allocation * upgrade node2 * enable allocation * wait for shards being recovered on node2 * disable allocation * upgrade node3 * enable allocation * wait for shards being recovered on node3 * disable allocation * ... * enable allocation I think this documentation update should go in 1.3, 1.4, 1.x and master branches. Closes #8218 Closes #7973.
dadoonet
added a commit
that referenced
this issue
Oct 24, 2014
When reading the [rolling upgrade process](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-upgrade.html#rolling-upgrades), you can see that we wrote: * disable allocation * upgrade node1 * upgrade node2 * upgrade node3 * ... * enable allocation That won't work as after a node has been removed and restarted, no shard will be allocated anymore. So closing node2 and remaining nodes, won't help to serve index and search request anymore. We should write: * disable allocation * upgrade node1 * enable allocation * wait for shards being recovered on node1 * disable allocation * upgrade node2 * enable allocation * wait for shards being recovered on node2 * disable allocation * upgrade node3 * enable allocation * wait for shards being recovered on node3 * disable allocation * ... * enable allocation I think this documentation update should go in 1.3, 1.4, 1.x and master branches. Closes #8218 Closes #7973.
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
When reading the [rolling upgrade process](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-upgrade.html#rolling-upgrades), you can see that we wrote: * disable allocation * upgrade node1 * upgrade node2 * upgrade node3 * ... * enable allocation That won't work as after a node has been removed and restarted, no shard will be allocated anymore. So closing node2 and remaining nodes, won't help to serve index and search request anymore. We should write: * disable allocation * upgrade node1 * enable allocation * wait for shards being recovered on node1 * disable allocation * upgrade node2 * enable allocation * wait for shards being recovered on node2 * disable allocation * upgrade node3 * enable allocation * wait for shards being recovered on node3 * disable allocation * ... * enable allocation I think this documentation update should go in 1.3, 1.4, 1.x and master branches. Closes elastic#8218 Closes elastic#7973.
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
When reading the [rolling upgrade process](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-upgrade.html#rolling-upgrades), you can see that we wrote: * disable allocation * upgrade node1 * upgrade node2 * upgrade node3 * ... * enable allocation That won't work as after a node has been removed and restarted, no shard will be allocated anymore. So closing node2 and remaining nodes, won't help to serve index and search request anymore. We should write: * disable allocation * upgrade node1 * enable allocation * wait for shards being recovered on node1 * disable allocation * upgrade node2 * enable allocation * wait for shards being recovered on node2 * disable allocation * upgrade node3 * enable allocation * wait for shards being recovered on node3 * disable allocation * ... * enable allocation I think this documentation update should go in 1.3, 1.4, 1.x and master branches. Closes elastic#8218 Closes elastic#7973.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When reading the rolling upgrade process, you can see that we wrote:
That won't work as after a node has been removed and restarted, no shard will be allocated anymore.
So closing node2 and remaining nodes, won't help to serve index and search request anymore.
We should write:
I think this documentation update should go in 1.3, 1.4, 1.x and master branches.
The text was updated successfully, but these errors were encountered: