Im curious why -XX:+DisableExplicitGC is used in our Elasticsearch install (via apt packages).
I often use an explicit GC to see how much memory is locked into the heap so that I can see how much memory we have free.
But of course with the current setup, there's now way to use this.
Was this done because some library was calling explicit GC in the background?
I'd love this have this enabled again, and realistically, ES shouldn't be setting this.