There is an issue where Groovy uses more permgen space than MVEL did, we've opened an issue to fix it here:
https://github.com/elasticsearch/elasticsearch/issues/7658 Until this is fixed, I believe putting the script on disk will have Elasticsearch compile it only once and help reduce the permgen usage from increasing, it can be referenced by name and still have parameters passed in. ;; Lee On Friday, October 10, 2014 8:21:44 AM UTC+2, Bernhard Berger wrote: > > Am 09.10.2014 22:40, schrieb Adam Cramer: > > We're experiencing a similar issue after having run ES successfully > > for several months without any major changes to our read/write > > patterns, data sizes or documents. This is on Java 7 and ES 1.3.4. > > > > Berhnard -- are you using scripting at all? The issue started popping > > up after we switched our scripting from MVEL to Groovy. > Yes, we also switched from MVEL to Groovy some months ago and the issue > started! > But we also changed a lot of other things in our code base, so I wasn't > sure about the cause. > > Our scripts are very simple (and are nearly the same as in MVEL), just > some lines like: `ctx._source.texts += text; ctx._source.state = state; > ctx._source.number+=1;`... > > Since yesterday everything runs fine (half of the old bulk size, Java > 8), but usually the memory problem appeared after about 1 week running a > node. > -- 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/45ceb77f-3664-488b-a91d-d6377b1f4506%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
