Hi
We are performing a rolling upgrade from 1.3.2 to 1.4.2.
We have turned off reallocation.
After upgrading 2 of 3 nodes we are receiving lots of warnings/errors in
the log file:
in node running 1.4.2:
[2015-01-13 12:22:09,902][WARN ][cluster.action.shard ]
[192.168.124.13] [edition][6] received shard failed for [edition][6],
node[FNnZJvgxQ6Or4i_Fe5H2Qw], [R], s[INITIALIZING], indexUUID
[johTS4GqSpOQbU6N5S7sCg], reason [Failed to start shard, message
[RecoveryFailedException[[edition][6]: Recovery failed from [Omega
Red][ckPNnMMdRZuZ5zU0XhrNCA][localhost][inet[/192.168.124.14:9300]]{master=true}
into
[192.168.124.12][FNnZJvgxQ6Or4i_Fe5H2Qw][localhost][inet[192.168.124.12/192.168.124.12:9300]]{master=true}];
nested: RemoteTransportException[[Omega
Red][inet[/192.168.124.14:9300]][index/shard/recovery/startRecovery]];
nested: IllegalArgumentException[No enum constant
org.apache.lucene.util.Version.LUCENE_4_10]; ]]
in node running 1.3.2:
[2015-01-13 12:16:20,152][WARN ][transport.netty ] [Omega Red]
Message not fully read (request) for [2303] and action
[index/shard/recovery/startRecovery], resetting
Are there any known issues when upgrading from 1.3.2 to 1.4.2?
Eventually the cluster became green. Does this mean we haven't lost any
data?
After upgrading node 1 we temporarily turned on reallocation again since it
did not seem to pick up its shards again. Should you turn on reallocation
after upgrading each node or after upgrading all nodes?
Do anyone know what the error messages mean?
/ daniel
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/7d428779-3860-47af-9daa-54b6bcd0cf96%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
