Yesterday, I have added a new node to my ES cluster and after that some
of the shards started to remain unassigned. These shards are the
replicas of the shards on the new node. When I inspected the reason, I
found out that this new node has a different ES version. The new one is
1.3.4 and the older ones are 1.3.2.
Does this difference cause the problem? If I upgrade the older ones,
does this solves the issue?
I installed ES via apt-get in Ubuntu. If I upgrade the current nodes via
apt-get, does this cause problems with old indices?
Yesterday, I have added a new node to my ES cluster and after that some of
the shards started to remain unassigned. These shards are the replicas of
the shards on the new node. When I inspected the reason, I found out that
this new node has a different ES version. The new one is 1.3.4 and the
older ones are 1.3.2.
Does this difference cause the problem? If I upgrade the older ones, does
this solves the issue?
I installed ES via apt-get in Ubuntu. If I upgrade the current nodes via
apt-get, does this cause problems with old indices?
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.