David Pilato 62d8b7ab97 Docs: rolling upgrade process seems incorrect ... 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.		2014-10-24 16:45:42 +02:00
..
as-a-service-win.asciidoc	Docs: Fixed typo in windows-as-a-service	2014-09-04 16:12:46 +02:00
as-a-service.asciidoc	Fix typo in docs	2014-05-14 12:36:35 +02:00
configuration.asciidoc	Docs: Changing ES_MAX_MEM default from '1gb' to '1g'	2014-07-25 12:50:59 +02:00
dir-layout.asciidoc	Docs: Fixed header levels in setup/dir-layout.asciidoc	2014-08-18 13:38:28 +02:00
repositories.asciidoc	Update repositories.asciidoc	2014-08-18 12:57:08 +02:00
upgrade.asciidoc	Docs: rolling upgrade process seems incorrect	2014-10-24 16:45:42 +02:00