# None of the configured nodes were available

**URL:** <https://discuss.elastic.co/t/none-of-the-configured-nodes-were-available/151030>\
**Category:** Elasticsearch\
**Created:** [October 4, 2018, 10:25am UTC](https://discuss.elastic.co/t/none-of-the-configured-nodes-were-available/151030 "2018-10-04T10:25:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mahendra\_Shinde](https://avatars.discourse-cdn.com/v4/letter/m/c57346/32.png) [@Mahendra\_Shinde](https://discuss.elastic.co/u/Mahendra_Shinde)\
**Post date:** [October 4, 2018, 10:25am UTC](https://discuss.elastic.co/t/none-of-the-configured-nodes-were-available/151030/1 "2018-10-04T10:25:10Z")

</div>

Hi,

I am getting frequent error for "None of the configured nodes were available" with transport client. My ES cluster is v6.4 and Transport client is generate as code below.  
This error of not **node available** is observed with new **elastic cloud only**. I reported to cloud team. And cloud team still investigating (even after 10days).

Any help ?  
val addresses = nodes.map { host =\> new TransportAddress(InetAddress.getByName(host), port) }  
val client = new PreBuiltXPackTransportClient(settings)  
.addTransportAddresses(addresses: \_\*)  
info(s"ElasticClient config =\> Nodes = ${nodes.toList} , port = $port clusterName $clusterName")

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [October 4, 2018, 11:02am UTC](https://discuss.elastic.co/t/none-of-the-configured-nodes-were-available/151030/2 "2018-10-04T11:02:10Z")

</div>

I don't know what will be the answer from the cloud support but anyway use the REST Client instead. The transport client is going to be removed at some point.

---

<div class="post-metadata">

**Author:** ![Mahendra\_Shinde](https://avatars.discourse-cdn.com/v4/letter/m/c57346/32.png) [@Mahendra\_Shinde](https://discuss.elastic.co/u/Mahendra_Shinde)\
**Post date:** [October 4, 2018, 11:20am UTC](https://discuss.elastic.co/t/none-of-the-configured-nodes-were-available/151030/3 "2018-10-04T11:20:07Z")

</div>

Thank you David,

Actually, we have many aggregations defined over transport client. It will be very big implementation task if we plan to migrate over rest.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [October 4, 2018, 12:10pm UTC](https://discuss.elastic.co/t/none-of-the-configured-nodes-were-available/151030/4 "2018-10-04T12:10:28Z")

</div>

What does prevent you to use the REST Client? It is able to define aggs as well...

---

<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:** [November 1, 2018, 12:10pm UTC](https://discuss.elastic.co/t/none-of-the-configured-nodes-were-available/151030/5 "2018-11-01T12:10:30Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.