Could you please check if my upgrade scenario given below will work
properly? I have three nodes in cluster (ES 1.3, no replication) and I want
to upgrade it to ES 1.4.
I wonder can I do the following:
Create three new nodes running ES 1.4
Add them to cluster
Configure replication "number_of_replicas": 1
4)Make sure replicas goes to new nodes by invoking curl -XPOST -d '{
"commands" : [ { "allocate" ... etc.
When all repicas are moved, enable one of new servers as master
Disable the old master
Stop old servers
Will this scenario work? Would it be the same to create snapshot and
restore it on new servers as new cluster?
The main point of why I'm not following official guide is: I want to be
able to come back quickly to previous configuration.
Yes but once you move a shard to a newer node then (usually) you can't
shift it back. This is due to changes in the underlying lucene segment.
You'll also need to make sure you have the same Java versions on all nodes
it you'll see problems.
But yes, snapshot and restore would be a better way to do this as you
maintain your previous state completely segregated.
On 12/01/2015 2:58 pm, "Krzysztof Madejski" krzysztof.madejski@epf.org.pl
wrote:
Hi,
Could you please check if my upgrade scenario given below will work
properly? I have three nodes in cluster (ES 1.3, no replication) and I want
to upgrade it to ES 1.4.
I wonder can I do the following:
Create three new nodes running ES 1.4
Add them to cluster
Configure replication "number_of_replicas": 1
4)Make sure replicas goes to new nodes by invoking curl -XPOST -d '{
"commands" : [ { "allocate" ... etc.
When all repicas are moved, enable one of new servers as master
Disable the old master
Stop old servers
Will this scenario work? Would it be the same to create snapshot and
restore it on new servers as new cluster?
The main point of why I'm not following official guide is: I want to be
able to come back quickly to previous configuration.
Yes but once you move a shard to a newer node then (usually) you can't
shift it back. This is due to changes in the underlying lucene segment.
You'll also need to make sure you have the same Java versions on all nodes
it you'll see problems.
But yes, snapshot and restore would be a better way to do this as you
maintain your previous state completely segregated.
On 12/01/2015 2:58 pm, "Krzysztof Madejski" <
krzysztof.madejski@epf.org.pl> wrote:
Hi,
Could you please check if my upgrade scenario given below will work
properly? I have three nodes in cluster (ES 1.3, no replication) and I want
to upgrade it to ES 1.4.
I wonder can I do the following:
Create three new nodes running ES 1.4
Add them to cluster
Configure replication "number_of_replicas": 1
4)Make sure replicas goes to new nodes by invoking curl -XPOST -d '{
"commands" : [ { "allocate" ... etc.
When all repicas are moved, enable one of new servers as master
Disable the old master
Stop old servers
Will this scenario work? Would it be the same to create snapshot and
restore it on new servers as new cluster?
The main point of why I'm not following official guide is: I want to be
able to come back quickly to previous configuration.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.