# Cluster Problem with short lived clients

**URL:** <https://discuss.elastic.co/t/cluster-problem-with-short-lived-clients/12048>\
**Category:** Elasticsearch\
**Created:** [May 21, 2013, 7:51am UTC](https://discuss.elastic.co/t/cluster-problem-with-short-lived-clients/12048 "2013-05-21T07:51:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Fabian\_Lange\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fabian_lange_2/32/1847_2.png) [@Fabian\_Lange\_2](https://discuss.elastic.co/u/Fabian_Lange_2)\
**Post date:** [May 21, 2013, 7:51am UTC](https://discuss.elastic.co/t/cluster-problem-with-short-lived-clients/12048/1 "2013-05-21T07:51:52Z")

</div>

Hi,  
we are running an elastic search 0.90 cluster, one index, having 3 replicas  
on 4 servers. Connected to that are 8 clients using the Java driver:

Settings settings = ImmutableSettings.settingsBuilder().put("node.name",  
CLIENT\_NAME)  
.build();  
Node node = NodeBuilder.nodeBuilder().clusterName(CLUSTER\_NAME).client(true)  
.settings(settings).node();  
client = node.client();

So the normal state of the cluster is GREEN(12,1)

Today, the cluster state was yellow. one of the Index Nodes was missing.  
The log file of that node said:

[2013-05-20 18:01:33,985][WARN][discovery.zen.ping.multicast] [node04]  
failed to connect to requesting node  
[batch-client][wkHJlBYpRAmZJOK0H6b4Pg][inet[/10.1.0.11:9303]]{client=true,  
data=false}

The log was full of these messages.

My theory is the following:  
We start up that batch node on regular interval on the said ip and port.  
The cluster tries to set up communication with that node.  
The node goes down (batch job done)  
Node04 went into some kind of error state, loosing connection to the  
cluster alltogether.

Does this make sense?  
Is this a bug?  
Should a short lived client only use http transport?

Fabian  
PS: Full stack trace which is perma-logged  
org.elasticsearch.transport.ConnectTransportException:  
[cd-client][inet[/10.1.0.11:9303]] connect\_timeout[30s]  
at  
org.elasticsearch.transport.netty.NettyTransport.connectToChannels(NettyTransport.java:671)  
at  
org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:610)  
at  
org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:580)  
at  
org.elasticsearch.transport.TransportService.connectToNode(TransportService.java:127)  
at  
org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing$Receiver$2.run(MulticastZenPing.java:539)  
at  
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)  
at  
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)  
at java.lang.Thread.run(Thread.java:722)

--  
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).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**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, 2:35am UTC](https://discuss.elastic.co/t/cluster-problem-with-short-lived-clients/12048/2 "2017-07-06T02:35:36Z")

</div>