# Elasticsearch trouble when client node is disconnected **URL:** \ **Category:** Elasticsearch\ **Created:** [April 14, 2015, 12:57pm UTC](https://discuss.elastic.co/t/elasticsearch-trouble-when-client-node-is-disconnected/23227 "2015-04-14T12:57:49Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Julio\_Cesar\_Tenganan](https://avatars.discourse-cdn.com/v4/letter/j/6de8d8/32.png) [@Julio\_Cesar\_Tenganan](https://discuss.elastic.co/u/Julio_Cesar_Tenganan)\ **Post date:** [April 14, 2015, 12:57pm UTC](https://discuss.elastic.co/t/elasticsearch-trouble-when-client-node-is-disconnected/23227/1 "2015-04-14T12:57:49Z")
Im using elasticsearch 1.4.0 I got a 9 node cluster setup with 4 data node 3 master node 2 clients I have an application which sends data concurrently to the cluster through client nodes. - Running high availability test One client node is disconnected and suddenly appear more information than the one I sent There is some exception handle when ClusterBlockException or EsRejectedExecutionException occur while bulkIndex is made? For now I retry failed index Is there any additional setup for client node? thanks -- 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/6b8f6439-db6b-4ce4-b630-bacf4fbc82c9%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/6b8f6439-db6b-4ce4-b630-bacf4fbc82c9%40googlegroups.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:19am UTC](https://discuss.elastic.co/t/elasticsearch-trouble-when-client-node-is-disconnected/23227/2 "2017-07-06T00:19:55Z")