• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

Elastic search configuration

#1
Hey everybody,

for a couple of month know, i'm running into memory issues with elasticsearch (0.20.5). Everytime we have a lot of traffic on the site (around 2.000 active users) elasticsearch is running out of memory and also kills the process of the apache.

Is anyone having the same issues? Maybe i can tune a little on the configuration? As soon as i deactive ES, the servers are running smoothly.

Thanks for your help.

Florian
 

Brogan

XenForo moderator
Staff member
#4
That should be enough.

You mention that it only happens when there are a lot of visitors (2000+).
Do you have many add-ons installed?
 

Mike

XenForo developer
Staff member
#5
  1. Consider upgrading to the latest version of ES.
  2. Ensure your indexes are optimized (use the latest version of the XFES add-on and optimize them via the admin CP).
  3. If all else fails, you'll need to allocate more memory to ES.
 
#6
We already upgraded to the latest ES Version (0.20.6.) and the index is optimized. There are also 2GB of memory allocated to ES.

That should be enough.

You mention that it only happens when there are a lot of visitors (2000+).
Do you have many add-ons installed?
Yeah, sadly we have. It seems that that's a problem too, i guess. But it's weird that the server runs smoothly, as soon as we deactivate the XFES add-on.
 

Brogan

XenForo moderator
Staff member
#7
I suspect you need to allocate more RAM to ES as Mike has said.

A rough rule of thumb seems to be around 1GB per 1 million posts.
 

CTXMedia

Formerly CyclingTribe
#11
Did you upgrade XFES from 1.0 to 1.0.1? The only reason I ask is that the newer version can optimise your search index and often reduces the size by up to 50% (on average) - so if you haven't yet optimised (in Tools > Elasticsearch Options) it might be worth doing. (y)

Cheers,
Shaun :D
 
#12
Yep, i've upgraded from 1.0 -> 1.0.1. I've already tried optimize the index. After it failed, i've deleted it and created a new one.

Our server host said, there are were lot of issues with java processes.
 

kontrabass

Well-known member
#13
@Crazy-Achmet Did you find a solution? Did you try increasing the memory allocated to ES? I don't know your board but I'm guessing you have 10M+ posts, so 2GB doesn't seem like near enough.