# 5.4, "None of the configured nodes are available", occurs only randomly
**URL:** https://discuss.elastic.co/t/5-4-none-of-the-configured-nodes-are-available-occurs-only-randomly/87180
**Category:** Elasticsearch
**Created:** [May 25, 2017, 8:18pm UTC](https://discuss.elastic.co/t/5-4-none-of-the-configured-nodes-are-available-occurs-only-randomly/87180 "2017-05-25T20:18:00Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@sina309](https://discuss.elastic.co/u/sina309)
#### Post date: [May 25, 2017, 8:18pm UTC](https://discuss.elastic.co/t/5-4-none-of-the-configured-nodes-are-available-occurs-only-randomly/87180/1 "2017-05-25T20:18:01Z")
Using ES 5.4, the configuration for local development is always fine, but starting the app in a production cluster giving me SOMETIMES:
"None of the configured nodes are available: [{#transport#-1}{mmm444333-IsVVBBFF}{[xxx.amazonaws.com](http://xxx.amazonaws.com)}{[xx.xx.xxx.xxx:9300](http://xx.xx.xxx.xxx:9300)}]]"
It happends quite randomly and quite often. I restart the container where the application is running a few more times and it connects over transport client to the cluster and index data. it can also happen that it connects a few times in a row and then it starts not connecting. Connecting i mean each time i start the container and the application builds the configuration initialization for ES.
I am using following parameters for Settings:
"[cluster.name](http://cluster.name)",
"client.transport.sniff" is always false,
and "client.transport.nodes\_sampler\_interval"
What might be the cause?
Best
---
### Author:  [@slovdahl](https://discuss.elastic.co/u/slovdahl)
#### Post date: [May 31, 2017, 10:15am UTC](https://discuss.elastic.co/t/5-4-none-of-the-configured-nodes-are-available-occurs-only-randomly/87180/2 "2017-05-31T10:15:43Z")
I've sometimes seen the same error message as well, and in my case the cause was long GC pauses. The default connection timeout is 5 seconds, at least for the Java transport client. If a garbage collection run in ES takes longer than that, the client will fail with that error.
Check your ES logs if there are any rows like this:
```
[2017-05-27T04:00:24,507][WARN][o.e.m.j.JvmGcMonitorService] [7LnWwxW] [gc][66855] overhead, spent [8.4s] collecting in the last [9.2s]
```
If yes, you need to increase the heap size for ES.
---
### Author:  [@sina309](https://discuss.elastic.co/u/sina309)
#### Post date: [May 31, 2017, 10:41am UTC](https://discuss.elastic.co/t/5-4-none-of-the-configured-nodes-are-available-occurs-only-randomly/87180/3 "2017-05-31T10:41:44Z")
I solved the problem. We were using a load balancer infront of the cluster and I was giving the host name of this load balancer to build the Transport with the underlying cluster. The IPs behind this LB were constantly changing, so we had connection sometimes and sometimes not. We initialized the Transport Client directly with the Node IPs (not LB) and it is now stable. Snippet:
> for (String clusterNode : clusterNodes) {
> client.addTransportAddress(new InetSocketTransportAddress(InetAddress.getByName(clusterNode), Integer.valueOf(9300)));
> }
My Best,
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [June 28, 2017, 10:42am UTC](https://discuss.elastic.co/t/5-4-none-of-the-configured-nodes-are-available-occurs-only-randomly/87180/4 "2017-06-28T10:42:17Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.