# Cluster issue -\> raiseTimeoutFailure **URL:** \ **Category:** Elasticsearch\ **Created:** [March 20, 2015, 12:59pm UTC](https://discuss.elastic.co/t/cluster-issue-raisetimeoutfailure/22777 "2015-03-20T12:59:03Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Ciprian\_2](https://avatars.discourse-cdn.com/v4/letter/c/9dc877/32.png) [@Ciprian\_2](https://discuss.elastic.co/u/Ciprian_2)\ **Post date:** [March 20, 2015, 12:59pm UTC](https://discuss.elastic.co/t/cluster-issue-raisetimeoutfailure/22777/1 "2015-03-20T12:59:03Z")
Hi, I have a java application that is indexind data in an Elasticsearch cluster(_3_ _nodes_). The ES is well configured and is working ok(indexing the received data from java). Cluster configuration for each node from /etc/elasticsearch/elasticsearch.yml ES\_MAX\_MEM: 2g ES\_MIN\_MEM: 2g bootstrap: mlockall: true cluster: name: clusterName discovery: zen: ping: multicast: enabled: false unicast: hosts: - elasticsearch-test-2-node-1 - elasticsearch-test-2-node-2 - elasticsearch-test-2-node-3 http: max\_initial\_line\_length: 48k index: number\_of\_replicas: 2 number\_of\_shards: 6 node: name: elasticsearch-test-2-node-3 threadpool: index: type: fixed size: 6 queue\_size: 1500 search: type: fixed size: 6 queue\_size: 1200 When I'm connecting the Es cluster(from java), I specify all the nodes : node1, node2, node3. The issue is appearing when I stop the 2 data nodes one by one(stop the elasticsearch). In this case the cluster health is yellow and i can see the remained master node(using "head" plugin). The _master_ has now _all the primary shards_. The replicas are "Unassigned". But the java application is not indexing any more the data. The next exception appear on java : org.elasticsearch.action.UnavailableShardsException: [indexName][2] [3] shardIt, [1] active : Timeout waiting for [1m], request: index {[indexName][typeName][Id], source[{ ..... }]} at org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction.raiseTimeoutFailure(TransportShardReplicationOperationAction.java:548) ~[elasticsearch-1.1.0.jar:na] at org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction$3.onTimeout(TransportShardReplicationOperationAction.java:538) ~[elasticsearch-1.1.0.jar:na] at org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:491) ~[elasticsearch-1.1.0.jar:na] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) ~[na:1.7.0\_51] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) ~[na:1.7.0\_51] at java.lang.Thread.run(Thread.java:745) ~[na:1.7.0\_51] - Shouldn't work properly the indexing in this case even with only the master? \* If I am going to kill also the master the next _logical_ exception appears org.elasticsearch.client.transport.NoNodeAvailableException: No node available at org.elasticsearch.client.transport.TransportClientNodesService$RetryListener.onFailure(TransportClientNodesService.java:263) ~[elasticsearch-1.1.0.jar:na] at org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:231) ~[elasticsearch-1.1.0.jar:na] at org.elasticsearch.client.transport.support.InternalTransportClient.execute(InternalTransportClient.java:106) ~[elasticsearch-1.1.0.jar:na] at org.elasticsearch.client.support.AbstractClient.update(AbstractClient.java:107) ~[elasticsearch-1.1.0.jar:na] -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/176b3f2e-9e18-4018-a4a9-46b009dfd3d2%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/176b3f2e-9e18-4018-a4a9-46b009dfd3d2%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [March 20, 2015, 4:45pm UTC](https://discuss.elastic.co/t/cluster-issue-raisetimeoutfailure/22777/2 "2015-03-20T16:45:10Z")
You shouldn't sent MIN and MAX just use ES\_HEAP\_SIZE and it will set both, you shouldn't also change the threadpools unless you understand and are aware of what they entail. I think the problem here would most likely be write consistency - > **[Index API | Elasticsearch Guide \[8.11\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-index_.html#index-consistency)** On 20 March 2015 at 05:59, Alex [turcanciprian87@gmail.com](mailto:turcanciprian87@gmail.com) wrote: > Hi, > > I have a java application that is indexind data in an Elasticsearch > cluster(_3_ _nodes_). The ES is well configured and is working > ok(indexing the received data from java). > Cluster configuration for each node from > /etc/elasticsearch/elasticsearch.yml > > ES\_MAX\_MEM: 2g > ES\_MIN\_MEM: 2g > bootstrap: > mlockall: true > cluster: > name: clusterName > discovery: > zen: > ping: > multicast: > enabled: false > unicast: > hosts: > - elasticsearch-test-2-node-1 > - elasticsearch-test-2-node-2 > - elasticsearch-test-2-node-3 > http: > max\_initial\_line\_length: 48k > index: > number\_of\_replicas: 2 > number\_of\_shards: 6 > node: > name: elasticsearch-test-2-node-3 > threadpool: > index: > type: fixed > size: 6 > queue\_size: 1500 > search: > type: fixed > size: 6 > queue\_size: 1200 > > When I'm connecting the Es cluster(from java), I specify all the nodes : > node1, node2, node3. > > The issue is appearing when I stop the 2 data nodes one by one(stop the > elasticsearch). In this case the cluster health is yellow and i can see the > remained master node(using "head" plugin). The _master_ has now _all the > primary shards_. The replicas are "Unassigned". But the java application > is not indexing any more the data. The next exception appear on java : > > org.elasticsearch.action.UnavailableShardsException: [indexName][2] [3] > shardIt, [1] active : Timeout waiting for [1m], request: index > {[indexName][typeName][Id], source[{ ..... }]} > at > org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction.raiseTimeoutFailure(TransportShardReplicationOperationAction.java:548) > ~[elasticsearch-1.1.0.jar:na] > at > org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction$3.onTimeout(TransportShardReplicationOperationAction.java:538) > ~[elasticsearch-1.1.0.jar:na] > at > org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:491) > ~[elasticsearch-1.1.0.jar:na] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > ~[na:1.7.0\_51] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > ~[na:1.7.0\_51] > at java.lang.Thread.run(Thread.java:745) ~[na:1.7.0\_51] > > - Shouldn't work properly the indexing in this case even with only the > master? \* > > If I am going to kill also the master the next _logical_ exception > appears > org.elasticsearch.client.transport.NoNodeAvailableException: No node > available > at > org.elasticsearch.client.transport.TransportClientNodesService$RetryListener.onFailure(TransportClientNodesService.java:263) > ~[elasticsearch-1.1.0.jar:na] > at > org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:231) > ~[elasticsearch-1.1.0.jar:na] > at > org.elasticsearch.client.transport.support.InternalTransportClient.execute(InternalTransportClient.java:106) > ~[elasticsearch-1.1.0.jar:na] > at > org.elasticsearch.client.support.AbstractClient.update(AbstractClient.java:107) > ~[elasticsearch-1.1.0.jar:na] > > -- > 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](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/176b3f2e-9e18-4018-a4a9-46b009dfd3d2%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/176b3f2e-9e18-4018-a4a9-46b009dfd3d2%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/176b3f2e-9e18-4018-a4a9-46b009dfd3d2%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/176b3f2e-9e18-4018-a4a9-46b009dfd3d2%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-JdbyjGdvh619yHnDO5%2BMYeiM%2B9sLh4H%2B4xbEAeOxozg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-JdbyjGdvh619yHnDO5%2BMYeiM%2B9sLh4H%2B4xbEAeOxozg%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 12:25am UTC](https://discuss.elastic.co/t/cluster-issue-raisetimeoutfailure/22777/3 "2017-07-06T00:25:20Z")