Are there memory leaks in ElasticSearch's TransportClient 5.4.3 or is my code flawed?

The ElasticSearch Java REST Client doesn't appear to have these issues.
I've switched over to it and haven't experienced out-of-memory errors. All relatively large byte arrays are released once the client is closed and scoped out.

1 Like