hello guys, in my system we adopted a pattern of adjusting the heap size parameter to 1G, but over time the service ends up consuming more than this value, is this ok or not? another question, does adjusting a limit for the heap size have any risk of problems? index corruption or something?
other question, why Elasticsearch does so much swap? how can i disable swap in Elasticsearch? Am I at risk with this?
Welcome to our community! 
We aren't all guys though.
Also please don't post pictures of text, logs or code. They are difficult to read, impossible to search and replicate (if it's code), and some people may not be even able to see them 
If you define a heap setting then Elasticsearch will stick to that. If you are seeing more memory usage attached to the process then that's system managed memory, not Elasticsearch.
If you go very small Elasticsearch probably won't run. If you go very large, then GC will be a problem when it happens. Otherwise, nope.
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.