# Elastic Search Transport Client(6.8.23) not able to connect to ES 7.17.10

**URL:** <https://discuss.elastic.co/t/elastic-search-transport-client-6-8-23-not-able-to-connect-to-es-7-17-10/336637>\
**Category:** Elasticsearch\
**Tags:** docker, language-clients\
**Created:** [June 22, 2023, 3:08am UTC](https://discuss.elastic.co/t/elastic-search-transport-client-6-8-23-not-able-to-connect-to-es-7-17-10/336637 "2023-06-22T03:08:40Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Abhilashsr2008](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/abhilashsr2008/32/144143_2.png) [@Abhilashsr2008](https://discuss.elastic.co/u/Abhilashsr2008)\
**Post date:** [June 22, 2023, 3:08am UTC](https://discuss.elastic.co/t/elastic-search-transport-client-6-8-23-not-able-to-connect-to-es-7-17-10/336637/1 "2023-06-22T03:08:40Z")

</div>

Hi Team  
My application is using the Elastic Search Transport Client(6.8.23) and am trying to connect to an Elasticsearch server which is 7.17.10 version. And am getting the below exception.

```auto
Caused by: NoNodeAvailableException[None of the configured nodes are available: [{#transport#-1}{NNvRVPQ1Qpan_KKOO5xRCw}{10.5.13.93:31400}]]
	at org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:250)

```

The cluster is in green state

````auto
{
  "name" : "elasticsearch-data-0",
  "cluster_name" : "elasticsearch-data-cluster",
  "cluster_uuid" : "Kc9N2jqyRxCZORw2VbZdPw",
  "version" : {
    "number" : "7.17.10",
    "build_flavor" : "default",
    "build_type" : "docker",
    "build_hash" : "fecd68e3150eda0c307ab9a9d7557f5d5fd71349",
    "build_date" : "2023-04-23T05:33:18.138275597Z",
    "build_snapshot" : false,
    "lucene_version" : "8.11.1",
    "minimum_wire_compatibility_version" : "6.8.0",
    "minimum_index_compatibility_version" : "6.0.0-beta1"
  },
  "tagline" : "You Know, for Search"
}```

Can someone please help to understand the issue .
````

---

<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:** [June 22, 2023, 5:48am UTC](https://discuss.elastic.co/t/elastic-search-transport-client-6-8-23-not-able-to-connect-to-es-7-17-10/336637/2 "2023-06-22T05:48:21Z")

</div>

It can not work. You must use the same versions. But some other things are wrong anyway:

You must upgrade to 7.17.10 and not a buggy version  
Or better to 8.8.1  
You need to switch to the new Java client.

---

<div class="post-metadata">

**Author:** ![Abhilashsr2008](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/abhilashsr2008/32/144143_2.png) [@Abhilashsr2008](https://discuss.elastic.co/u/Abhilashsr2008)\
**Post date:** [June 22, 2023, 1:13pm UTC](https://discuss.elastic.co/t/elastic-search-transport-client-6-8-23-not-able-to-connect-to-es-7-17-10/336637/3 "2023-06-22T13:13:59Z")

</div>

yes thats the plan .. but ideally the libraries are forward compatible right .. even the official documentation says library upgrade as the last step during ES migration .

---

<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:** [June 22, 2023, 2:52pm UTC](https://discuss.elastic.co/t/elastic-search-transport-client-6-8-23-not-able-to-connect-to-es-7-17-10/336637/4 "2023-06-22T14:52:11Z")

</div>

> [@Abhilashsr2008](#):
>
> but ideally the libraries are forward compatible right

No. Not within major versions, and specifically with the removed TransportClient.

---

<div class="post-metadata">

**Author:** ![Abhilashsr2008](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/abhilashsr2008/32/144143_2.png) [@Abhilashsr2008](https://discuss.elastic.co/u/Abhilashsr2008)\
**Post date:** [June 22, 2023, 5:42pm UTC](https://discuss.elastic.co/t/elastic-search-transport-client-6-8-23-not-able-to-connect-to-es-7-17-10/336637/5 "2023-06-22T17:42:43Z")

</div>

Sorry for asking it again. As per this documentation : [Transport Client | Java Transport Client (deprecated) [7.17] | Elastic](https://www.elastic.co/guide/en/elasticsearch/client/java-api/current/transport-client.html)  
Transport client is not getting removed as part of 7.17 , its getting deprecated right .. so ideally i should be able to access 7.17 using the 6.18 transport client libs right

---

<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:** [June 22, 2023, 6:06pm UTC](https://discuss.elastic.co/t/elastic-search-transport-client-6-8-23-not-able-to-connect-to-es-7-17-10/336637/6 "2023-06-22T18:06:18Z")

</div>

No. I don't think this will work. If you want to access a 6.8 cluster, use a 6.8 TransportClient.  
If you want to access a 7.17 cluster, use a 7.17 TransportClient. Although I recommend using the new Java client.

---

<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 20, 2023, 6:06pm UTC](https://discuss.elastic.co/t/elastic-search-transport-client-6-8-23-not-able-to-connect-to-es-7-17-10/336637/7 "2023-07-20T18:06:39Z")

</div>

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