An update with more details, we have set MaxMetaspaceSize and have been
running for a while now. The number of loaded classes seems to be under
control as well as the metaspace size.
We are however still seeing a slow/steady increase of the "Internal"
category as reported by Native Memory Trackin
We have noticed on a high traffic instance of our application that the
number of loaded classes continues to grow, this in turn increases the
amount of Metaspace and native memory used by the JVM. Moving forward we
are working on a safe value for MaxMetaspaceSize which should eventually
trigger a