(#628) Added io.netty.allocator.numDirectArenas=0 flag to jvm.options

[andrx]

(#628) Added io.netty.allocator.numDirectArenas=0 flag to overcome RAM issues on ES >= 7.4.0

[elasticmachine]

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

[jmlrt]

⛴

[jmlrt]

jenkins test this please

[jmlrt]

jenkins test this please

[jmlrt]

⛴

[jmlrt]

@andrx I was ready to merge your PR but it seems that jvm options will change in next Elasticsearch release elastic/elasticsearch#48252

[andrx]

@jmlrt hey, no problem... great to hear.
so, will you update the template accordingly or I misunderstood how it's going to work

[jmlrt]

Yeah I'll need to check in details what is required

If there is just things to change in the current jvm.options template, maybe I'll be able to post changes required to this PR so you can include them before merging.

If a different solution is required (maybe use default jvm.options file from Elasticsearch package and allow to fully overwrite it only if some variables are provided to ansible) I'll create a new PR and close this one.

Anyway thank you for your work on this PR 👍

[andrx]

Sure, great that it will be sorted with ES 7.5

[jmlrt]

@andrx, I was finally able to merge #637 which handle jvm options. I'm closing your PR. Thank you for your work here👍

[andrx]

@jmlrt just curious when do you plan to release those. at the moment i temporarily pointed it to master but would like to set a specific version.
thanks in advance

[jmlrt]

We were waiting #637 merge to create 7.5.0 release and may still have a couple of small pr to pass, so the release should come in the beginning of next week.

[andrx]

got it. thank you!