# How many Transport Clients can a Elasticsearch cluster have?

**URL:** <https://discuss.elastic.co/t/how-many-transport-clients-can-a-elasticsearch-cluster-have/60252>\
**Category:** Elasticsearch\
**Created:** [September 12, 2016, 5:37am UTC](https://discuss.elastic.co/t/how-many-transport-clients-can-a-elasticsearch-cluster-have/60252 "2016-09-12T05:37:32Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![javanna](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/javanna/32/4698_2.png) [@javanna](https://discuss.elastic.co/u/javanna)\
**Post date:** [September 12, 2016, 8:14am UTC](https://discuss.elastic.co/t/how-many-transport-clients-can-a-elasticsearch-cluster-have/60252/2 "2016-09-12T08:14:49Z")

</div>

The transport client is a normal client, it doesn't join the cluster or anything like that. That said it is recommended that the transport client is a singleton in your application, it is thread-safe hence the same instance should be used for all your requests to elasticsearch. The problems that may arise from using more instances are more on the client side though than on the server side. Maybe too many connection handles also on the server side.

---

_[View the full topic](https://discuss.elastic.co/t/how-many-transport-clients-can-a-elasticsearch-cluster-have/60252)._