Elastic search using more RAM

Please format your code, logs or configuration files using </> icon as explained in this guide and not the citation button. It will make your post more readable.

Or use markdown style like:

```
CODE
```

This is the icon to use if you are not using markdown format:

There's a live preview panel for exactly this reasons.

Lots of people read these forums, and many of them will simply skip over a post that is difficult to read, because it's just too large an investment of their time to try and follow a wall of badly formatted text.
If your goal is to get an answer to your questions, it's in your interest to make it as easy to read and understand as possible.
Please update your post.

Coming back to your question, you need to understand how all that works. Actually, indices are stored on disk on the FileSystem. The OS has a FileSystem cache which is used a lot in this context. That's probably why you are seeing that.
That's why we recommend:

  • having only elasticsearch service running on a machine
  • do not set more than half of the memory to the heap size
  • do not set more than 30gb of memory to the heap size

Here, 26gb of RAM for 8gb of HEAP sounds good to me as long as your HEAP is not under pressure, in which case you can increase the HEAP up to 13gb or start new nodes.

My 2 cents