Hi,
Our Elastic Search cluster has just gone yellow, and I can't work out why.
A single shard on one index on one of our four servers is showing as yellow
(INITIALIZING) and has been that way for ~20 minutes.
In the log file on that server I'm seeing:
[12:13:42,188][WARN ][transport.netty ] [prd-elastic-2] Message notfully read
(response) for [2289097] handler org.elasticsearch.action.support.nodes.
TransportNodesOperationAction$AsyncAction$4@7f0608e3, error [false],resetting
[12:13:42,470][WARN ][transport.netty ] [prd-elastic-2] Message notfully read
(response) for [2289095] handler org.elasticsearch.action.support.nodes.
TransportNodesOperationAction$AsyncAction$4@1455d93e, error [false],resetting
[12:13:42,667][WARN ][transport.netty ] [prd-elastic-2] Message notfully read
(response) for [2289096] handler org.elasticsearch.action.support.nodes.
TransportNodesOperationAction$AsyncAction$4@45581337, error [false],resetting
[12:14:02,199][WARN ][transport.netty ] [prd-elastic-2] Message notfully read
(response) for [2289369] handler org.elasticsearch.action.support.nodes.
TransportNodesOperationAction$AsyncAction$4@7e2584ea, error [false],resetting
[12:14:02,200][WARN ][transport.netty ] [prd-elastic-2] Message notfully read
(response) for [2289371] handler org.elasticsearch.action.support.nodes.
TransportNodesOperationAction$AsyncAction$4@51395f59, error [false],resetting
[12:14:02,431][WARN ][transport.netty ] [prd-elastic-2] Message notfully read
(response) for [2289370] handler org.elasticsearch.action.support.nodes.
TransportNodesOperationAction$AsyncAction$4@2bb033a9, error [false],resetting
[12:49:20,084][WARN ][transport.netty ] [prd-elastic-2] Message notfully read
(response) for [2298845] handler future(org.elasticsearch.indices.recovery.
RecoveryTarget$3@3bdd6de), error [true], resetting
[12:49:21,204][WARN ][transport.netty ] [prd-elastic-2] Message notfully read
(response) for [2298852] handler future(org.elasticsearch.indices.recovery.
RecoveryTarget$3@4ed4f235), error [true], resetting
[12:49:23,399][WARN ][transport.netty ] [prd-elastic-2] Message notfully read
(response) for [2298860] handler future(org.elasticsearch.indices.recovery.
RecoveryTarget$3@39f1c3c8), error [true], resetting
[12:49:26,557][WARN ][transport.netty ] [prd-elastic-2] Message notfully read
(response) for [2298885] handler future(org.elasticsearch.indices.recovery.
RecoveryTarget$3@63afb865), error [true], resetting
[13:04:16,616][WARN ][transport.netty ] [prd-elastic-2] Message notfully read
(response) for [2305703] handler org.elasticsearch.action.support.nodes.
TransportNodesOperationAction$AsyncAction$4@23a15cb3, error [false],resetting
[13:04:16,616][WARN ][transport.netty ] [prd-elastic-2] Message notfully read
(response) for [2305702] handler org.elasticsearch.action.support.nodes.
TransportNodesOperationAction$AsyncAction$4@36ccfe0b, error [false],resetting
[13:04:23,550][WARN ][transport.netty ] [prd-elastic-2] Message notfully read
(response) for [2305704] handler org.elasticsearch.action.support.nodes.
TransportNodesOperationAction$AsyncAction$4@66fcc314, error [false],resetting
Not entirely sure what this means or how to fix it… a preliminary Google
search suggests this may be caused by mixed Elastic Search versions, but
all nodes are running 0.19.12.
Any advice would be welcomed.
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
