I have recently taken on the task of managing our existing ES index and in doing so had to alter the index in a way to allow sorting on certain fields. Ever since my updates to the index mapping and an increase in total traffic I/O we have been seeing more and more memory leaks where we could go from 3GB/28GB to 27GB/28GB in less than an hour even though a top command reveals ES only taking up 14% of the total memory.
Here is our configuration:
1 node w/ 28GB RAM on Azure VM (Ubuntu)
1 Index w/ 83.4GB of data
What other information would you like to see to help debug? Thanks!