# Java High Level Client Nodes Info API

**URL:** https://discuss.elastic.co/t/java-high-level-client-nodes-info-api/255885
**Category:** Elasticsearch
**Tags:** language-clients
**Created:** [November 18, 2020, 6:45pm UTC](https://discuss.elastic.co/t/java-high-level-client-nodes-info-api/255885 "2020-11-18T18:45:53Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![tberne](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tberne/32/648_2.png) [@tberne](https://discuss.elastic.co/u/tberne)
#### Post date: [November 18, 2020, 6:45pm UTC](https://discuss.elastic.co/t/java-high-level-client-nodes-info-api/255885/1 "2020-11-18T18:45:53Z")

</div>

Hi!  
I'm in a process of migration between Java Transport Client and Java High Level Client.  
Transport client had a `nodesInfo` API (we used `client.admin().cluster().prepareNodesInfo().execute().get().getNodes()` to be more precise) and I wasn't able to find a replacement in Java High Level Client (7.10).  
I've reached to this [Github issue](https://github.com/elastic/elasticsearch/issues/27205) that says that nodes info wasn't required for high level client completeness.  
So, I ask: Is there an alternative to Transport Client's nodes info API in Java High-Level REST Client?  
Thank you in advance!

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/c/e/ce1a4612749a84f216d81ed43934fdbaacde6a23.png)

---

<div class="post-metadata">

### Author: ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [November 18, 2020, 7:38pm UTC](https://discuss.elastic.co/t/java-high-level-client-nodes-info-api/255885/2 "2020-11-18T19:38:38Z")

</div>

Not in the high-level REST client, but you can call the REST API directly via the low-level client (which you can obtain via `RestHighLevelClient#getLowLevelClient()`).

Out of interest what were you using the nodes info API for in your client application? Perhaps there's another way to achieve the same goal, or perhaps you have a compelling enough case to add the nodes info API to the high-level client.

---

<div class="post-metadata">

### Author: ![tberne](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tberne/32/648_2.png) [@tberne](https://discuss.elastic.co/u/tberne)
#### Post date: [November 18, 2020, 7:43pm UTC](https://discuss.elastic.co/t/java-high-level-client-nodes-info-api/255885/3 "2020-11-18T19:43:57Z")

</div>

Thank you for your response, @DavidTurner .  
Well, our product ([LumisXP](https://lumisxp.lumis.com.br/)) use Elasticsearch as a NoSQL database for our Customer Experience Platform.  
We use the nodes info API as both gathering Elasticsearch nodes JVM usage statistics and health checking (check Elasticsearch version to know if it is supported --- in each Elasticsearch cluster node).

---

<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: [December 16, 2020, 7:43pm UTC](https://discuss.elastic.co/t/java-high-level-client-nodes-info-api/255885/4 "2020-12-16T19:43:59Z")

</div>

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