I was running resiliency tests for Elasticsearch and found that when Master or Data node recovers after being killed, my client library throws org.elasticsearch.cluster.block.ClusterBlockException: blocked by: [SERVICE_UNAVAILABLE/1/state not recovered / initialized]; up to a second after recovery. It seems for me that client tries to send request to not fully recovered node, which causes this error. However, this does not seems to be right for me.
Does anyone has such issues?
Java client - 1.3.2 (provided by spring-data-elasticsearch:1.1.2.RELEASE) Elasticsearch - 1.5
It might be an issue with old 1.3.2 client. Is there any way to track change list of Client releases?
That makes sense, but basically that means that my requests will be lost under traffic when the node comes up.
Isn't it a Master node decision when node is ready for processing requests? Why it includes it in availability pool when it is not ready?
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.