# High Memory usage after migrating from Transport Client to Rest Client

**URL:** https://discuss.elastic.co/t/high-memory-usage-after-migrating-from-transport-client-to-rest-client/341963
**Category:** Elasticsearch
**Created:** [August 30, 2023, 9:31am UTC](https://discuss.elastic.co/t/high-memory-usage-after-migrating-from-transport-client-to-rest-client/341963 "2023-08-30T09:31:09Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![emmning](https://avatars.discourse-cdn.com/v4/letter/e/59ef9b/32.png) [@emmning](https://discuss.elastic.co/u/emmning)
#### Post date: [August 30, 2023, 9:31am UTC](https://discuss.elastic.co/t/high-memory-usage-after-migrating-from-transport-client-to-rest-client/341963/1 "2023-08-30T09:31:09Z")

</div>

Hello,

After migrating from Transport Client to Rest Client we discoverd some nodes in the Elasticsearch cluster had high memory usage and these nodes was not responding to **cat/nodes** request.

I'm running Eclipse memory analyzer to analyze the hprof dump :

 ![截屏2023-08-30 下午5.29.48](https://us1.discourse-cdn.com/elastic/original/3X/5/b/5b9e063431eb16f927aac5abc24e76d6cf39eb27.png)  
 ![截屏2023-08-30 下午5.28.37](https://us1.discourse-cdn.com/elastic/original/3X/9/9/990722e6ec4a2742853505c270c82a9de0a73a27.jpeg)  
 ![截屏2023-08-30 下午5.28.21](https://us1.discourse-cdn.com/elastic/original/3X/5/9/5928d0e0bf6c7c675fb1b00c96983a944392ef79.jpeg)

Elasticsearch version:7.9.1  
java version:1.8  
total heap space size:32GB

Any help would be greatly appreciated.

---

<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: [September 27, 2023, 9:31am UTC](https://discuss.elastic.co/t/high-memory-usage-after-migrating-from-transport-client-to-rest-client/341963/2 "2023-09-27T09:31:37Z")

</div>

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