One single instance.

-- 
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet <https://twitter.com/dadoonet> | @elasticsearchfr 
<https://twitter.com/elasticsearchfr> | @scrutmydocs 
<https://twitter.com/scrutmydocs>



> Le 4 févr. 2015 à 10:12, Abid Hussain <[email protected]> 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 [email protected] 
> <mailto:[email protected]>.
> 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?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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/7EAB46C8-AB2C-4AFA-9A6B-C46CE024F8F5%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.

Reply via email to