# Recommended setup for using TransportClient in Webapp

**URL:** <https://discuss.elastic.co/t/recommended-setup-for-using-transportclient-in-webapp/21969>\
**Category:** Elasticsearch\
**Created:** [February 4, 2015, 9:12am UTC](https://discuss.elastic.co/t/recommended-setup-for-using-transportclient-in-webapp/21969 "2015-02-04T09:12:31Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Abid\_Hussain](https://avatars.discourse-cdn.com/v4/letter/a/dfb087/32.png) [@Abid\_Hussain](https://discuss.elastic.co/u/Abid_Hussain)\
**Post date:** [February 4, 2015, 9:12am UTC](https://discuss.elastic.co/t/recommended-setup-for-using-transportclient-in-webapp/21969/1 "2015-02-04T09:12:31Z")

</div>

Hi all,

I wonder what is the recommended setup for using TransportClient in a  
multi-threaded environment with parallel search requests (i.e. a webapp).

Basically, I see two alternatives:

1. Using a single instance of TransportClient for all incoming search  
requests
2. Creating a new instance of TransportClient for each incoming search  
request

What do you think?

Regards,

Abid

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/ba868b91-2ff2-47eb-9ebe-6ce481211a3d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ba868b91-2ff2-47eb-9ebe-6ce481211a3d%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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:** [February 4, 2015, 9:36am UTC](https://discuss.elastic.co/t/recommended-setup-for-using-transportclient-in-webapp/21969/2 "2015-02-04T09:36:42Z")

</div>

One single instance.

--  
David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com)  
@dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs)

> Le 4 févr. 2015 à 10:12, Abid Hussain [hussain@novacom.mygbiz.com](mailto:hussain@novacom.mygbiz.com) a écrit :
> 
> Hi all,
> 
> I wonder what is the recommended setup for using TransportClient in a multi-threaded environment with parallel search requests (i.e. a webapp).
> 
> Basically, I see two alternatives:  
> Using a single instance of TransportClient for all incoming search requests  
> Creating a new instance of TransportClient for each incoming search request
> 
> What do you think?
> 
> Regards,
> 
> Abid
> 
> --  
> You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com) [mailto:elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/ba868b91-2ff2-47eb-9ebe-6ce481211a3d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ba868b91-2ff2-47eb-9ebe-6ce481211a3d%40googlegroups.com) [https://groups.google.com/d/msgid/elasticsearch/ba868b91-2ff2-47eb-9ebe-6ce481211a3d%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ba868b91-2ff2-47eb-9ebe-6ce481211a3d%40googlegroups.com?utm_medium=email&utm_source=footer).  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout) [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/7EAB46C8-AB2C-4AFA-9A6B-C46CE024F8F5%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/7EAB46C8-AB2C-4AFA-9A6B-C46CE024F8F5%40pilato.fr).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![Abid\_Hussain](https://avatars.discourse-cdn.com/v4/letter/a/dfb087/32.png) [@Abid\_Hussain](https://discuss.elastic.co/u/Abid_Hussain)\
**Post date:** [February 4, 2015, 10:17am UTC](https://discuss.elastic.co/t/recommended-setup-for-using-transportclient-in-webapp/21969/3 "2015-02-04T10:17:43Z")

</div>

Thanks a lot for you quick help.

Am Mittwoch, 4. Februar 2015 10:36:52 UTC+1 schrieb David Pilato:

> One single instance.
> 
> --  
> _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com)  
> [http://Elasticsearch.com](http://Elasticsearch.com)_  
> @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr  
> [https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr) | @scrutmydocs  
> [https://twitter.com/scrutmydocs](https://twitter.com/scrutmydocs)
> 
> Le 4 févr. 2015 à 10:12, Abid Hussain \<[hus...@novacom.mygbiz.com](mailto:hus...@novacom.mygbiz.com)  
> \<javascript:\>\> a écrit :
> 
> Hi all,
> 
> I wonder what is the recommended setup for using TransportClient in a  
> multi-threaded environment with parallel search requests (i.e. a webapp).
> 
> Basically, I see two alternatives:
> 
> 1. Using a single instance of TransportClient for all incoming search  
> requests
> 2. Creating a new instance of TransportClient for each incoming search  
> request
> 
> What do you think?
> 
> Regards,
> 
> Abid
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/ba868b91-2ff2-47eb-9ebe-6ce481211a3d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ba868b91-2ff2-47eb-9ebe-6ce481211a3d%40googlegroups.com)  
> [https://groups.google.com/d/msgid/elasticsearch/ba868b91-2ff2-47eb-9ebe-6ce481211a3d%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/ba868b91-2ff2-47eb-9ebe-6ce481211a3d%40googlegroups.com?utm_medium=email&utm_source=footer)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/d47da39d-26f4-418a-a5b8-45a4158be04c%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d47da39d-26f4-418a-a5b8-45a4158be04c%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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 6, 2017, 12:35am UTC](https://discuss.elastic.co/t/recommended-setup-for-using-transportclient-in-webapp/21969/4 "2017-07-06T00:35:01Z")

</div>


