Elasticsearch--java jest client--datapoint needed

Hello Folks,
I posted on this topic yesterday and didnt hear back, thought I'd try
again, has anyone used the elasticsearch java jest library and done perf
tests with it running under tomcat. We have a rest service that abstracts
away the jest library and performs crud functionality against an
elasticsearch cluster and we're currently having some issues with running
out of operating system sockets/file descriptors during our load test when
using this library within a very short period of time, before I make any
major changes I plan to:

  1. Tweak the associated httpclient connection manager configs
  2. Tweak environment linux settings

Finally if the above don't make a difference I plan to:
3) Rewrite the code using the elasticsearch java API instead

Would love to hear from the community about any learning around perf tests
around the library.

Regards

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

Hi Saikat,

I have replied to you through our support but maybe it is not reached.

Well first please create only one JestClient it is singleton and configure
it as multi threaded. That is very much possibility why you are having too
many open sockets errors.

You can configure max open connections and per route connections if
necessary. Please see https://github.com/searchbox-io/Jest/wiki/Changelog
v0.0.3

To see all in action check JestClientFactoryTest.multiThreadedClientCreation
for sample usages.

On Tuesday, April 9, 2013 6:24:22 PM UTC+3, Saikat Kanjilal wrote:

Hello Folks,
I posted on this topic yesterday and didnt hear back, thought I'd try
again, has anyone used the elasticsearch java jest library and done perf
tests with it running under tomcat. We have a rest service that abstracts
away the jest library and performs crud functionality against an
elasticsearch cluster and we're currently having some issues with running
out of operating system sockets/file descriptors during our load test when
using this library within a very short period of time, before I make any
major changes I plan to:

  1. Tweak the associated httpclient connection manager configs
  2. Tweak environment linux settings

Finally if the above don't make a difference I plan to:
3) Rewrite the code using the elasticsearch java API instead

Would love to hear from the community about any learning around perf tests
around the library.

Regards

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