Es version that we are using is 2.5
The set up of the ES search service is ES_JAVA_OPTS="-Xms1g -Xmx1g" and having bootstrap.mlockall: true on a windows server just hosting ES service. The window server box itself has 8gb of memory overall.
We are doing load testing on search and see how the ES service could cope with the load. The load is we have 125 concurrent search requests hitting the ES service. We notice the memory starting to increase and gone beyond the 1GB that we told ES search could have, after 30 minutes gone ES service uses all 8GB of the box.
Open inspection using resource monitor in the windows server i could see the memory usage for ES is (Private 1,686MB, which it should be only 1GB ) as well as Shareable KB is 5,392 KB.
My question is why it does not honour the 1GB limit that we set it?
And is it normal to have such a high Shareable memory being used by ES?