You shouldn't run multiple versions unless you are upgrading, so it would
make sense to upgrade the other nodes ASAP.
The logs on your nodes should also shed some more light on the problem.
On 6 November 2014 19:29, Umutcan umut...@gamegos.com wrote:
Hi,
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?
Thanks,
Umutcan
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/elasticsearch/545B3152.1080606%40gamegos.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAF3ZnZmHbWBotFmt4dLxUmnG2v95f5nwc%2Bz27cEWpTDnp-vv9Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
