By the way, this is a huge problem. The Elasticsearch JVM will be trying to run garbage collection constantly, one attempt after another, because the JVM is set to auto-trigger garbage collection at 75% utilization. This also leads to slow search, slow indexing, slow everything. This is a tremendous amount of memory pressure, and the only way to correct this is to either close a lot more indices, or to add more nodes to spread the shard count out more. Even adding more RAM to permit a 30G heap will only help a tiny bit.
2 Likes