Page History

...

The ResourceManager only needs two items from the JVM: the maximum size of the heap and the amount of the heap in use. To allow Geode to call APIs that did not exist in Java 8, we will add a single interface, HeapUsageProvider that a user can implement with a class that must have a zero-argument constructor. The user will specify that it wants to use its class by setting the system property "geode.heapUsageProviderClassName" to the name of their class. This system property would need to be set on each server that they want it to be used on. Their class will also need to be made loader loadable on the server by adding it to the server's class path or deploying it to the server. Geode will load the class when the Cache is created. If the class fails to load, or a new instance can not be created, or the instance does not implement HeapUsageProvider, then the Cache creation will fail with an exception describing the problem. HeapUsageProvider implementations must return meaningful values when asked for the maximum and used heap amounts. It can optionally send notifications to Geode when the used memory changes.

By default Geode supplies its own internal HeapUsageProvider which will be used if the user does not set the "geode.heapUsageProviderClassName" system property.

A draft PR of this solution can be found here: https://github.com/apache/geode/pull/7456

...