Re: ES load test ended up with out of memory error after enabling the clustering

Glad you solved it. You're welcome. Best, Jörg On Sat, Apr 25, 2015 at 8:12 PM, Manjula Piyumal wrote: > Hi Jörg, > > You are correct, there was a problem in my query client which produced the > query load than expected. Thanks again for your help and sorry for the > inconvenience. > > Thanks

Re: ES load test ended up with out of memory error after enabling the clustering

Hi Jörg, You are correct, there was a problem in my query client which produced the query load than expected. Thanks again for your help and sorry for the inconvenience. Thanks Manjula On Fri, Apr 17, 2015 at 9:18 AM, Manjula Piyumal wrote: > Hi Jörg, > > Thanks a lot for your help. May I know

Re: ES load test ended up with out of memory error after enabling the clustering

Hi Jörg, Thanks a lot for your help. May I know what is the size of one record that you are publishing to ES. And did you do any configuration changes to the default configurations? Thanks Manjula On Fri, Apr 17, 2015 at 2:51 AM, joergpra...@gmail.com < joergpra...@gmail.com> wrote: > I have th

Re: ES load test ended up with out of memory error after enabling the clustering

I have thousands of concurrent indexing/queries running per second on non-virtualized servers. 4G heap is ok, it is more than enough, there should be other reasons for OOM I am sure. Maybe Bigdesk can help for monitoring heap and cache eviction rates. I think I can not help any more - no experie

Re: ES load test ended up with out of memory error after enabling the clustering

Hi Jörg, Sorry, my bad. It's a typo, I have used 4GB heap for all three ES servers. I have tried without limiting the cache size as the first attempt. But it also got the out of memory error. Am I not missing any other configuration? Or is this load is too much for 4GB heap? Thanks Manjula --

Re: ES load test ended up with out of memory error after enabling the clustering

Did you assign different heap sizes? Please use same heap size for all data nodes. Do not limit cache to 30%, this is very small. Let ES use the default settings. Jörg On Thu, Apr 16, 2015 at 5:43 PM, Manjula Piyumal wrote: > Hi all, > > I am trying to run load test with ES to identify system r

ES load test ended up with out of memory error after enabling the clustering

Hi all, I am trying to run load test with ES to identify system requirements and optimum configurations with respect to my load. I have 10 data publishing tasks and 100 data consuming tasks in my load test. Data publisher : Each publisher publishes data in every minute and it publishes 1700 re