Recommended setup for using TransportClient in Webapp

Elastic Stack Elasticsearch
1

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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/ba868b91-2ff2-47eb-9ebe-6ce481211a3d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

2

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 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.
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 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.
For more options, visit https://groups.google.com/d/optout.

3

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
@dadoonet https://twitter.com/dadoonet | @elasticsearchfr
https://twitter.com/elasticsearchfr | @scrutmydocs
https://twitter.com/scrutmydocs

Le 4 févr. 2015 à 10:12, Abid Hussain <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 <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?utm_medium=email&utm_source=footer
.
For more options, visit 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/d47da39d-26f4-418a-a5b8-45a4158be04c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.