Configure Data Eviction
Use eviction controllers to configure the eviction-attributes region attribute settings to keep your region within a specified limit.
Eviction controllers monitor region and memory use and, when the limit is reached, remove older entries to make way for new data. For heap percentage, the controller used is the GemFire resource manager, configured in conjunction with the JVM’s garbage collector for optimum performance.
Configure data eviction as follows. You do not need to perform these steps in the sequence shown.
Decide whether to evict based on:
- Entry count (useful if your entry sizes are relatively uniform).
- Total bytes used. In partitioned regions, this is set using
local-max-memory. In non-partitioned, it is set in
- Percentage of application heap used. This uses the GemFire resource manager. When the manager determines that eviction is required, the manager orders the eviction controller to start evicting from all regions where the eviction algorithm is set to
lru-heap-percentage. Eviction continues until the manager calls a halt. GemFire evicts the least recently used entry hosted by the member for the region. See Managing Heap and Off-heap Memory.
Decide what action to take when the limit is reached:
- Locally destroy the entry.
- Overflow the entry data to disk. See Persistence and Overflow.
Decide the maximum amount of data to allow in the member for the eviction measurement indicated. This is the maximum for all storage for the region in the member. For partitioned regions, this is the total for all buckets stored in the member for the region - including any secondary buckets used for redundancy.
Decide whether to program a custom sizer for your region. If you are able to provide such a class, it might be faster than the standard sizing done by GemFire. Your custom class must follow the guidelines for defining custom classes and, additionally, must implement
org.apache.geode.cache.util.ObjectSizer. See Requirements for Using Custom Classes in Data Caching.
// Create an LRU memory eviction controller with max bytes of 1000 MB // Use a custom class for measuring the size of each object in the region <region-attributes refid="REPLICATE"> <eviction-attributes> <lru-memory-size maximum="1000" action="overflow-to-disk"> <class-name>com.myLib.MySizer</class-name> <parameter name="name"> <string>Super Sizer</string> </parameter> </lru-memory-size> </eviction-attributes> </region-attributes>
// Create a memory eviction controller on a partitioned region with max bytes of 512 MB <region name="demoPR"> <region-attributes refid="PARTITION"> <partition-attributes local-max-memory="512" total-num-buckets="13"/> <eviction-attributes> <lru-memory-size action="local-destroy"/> <class-name>org.apache.geode.cache.util.ObjectSizer </class-name> </eviction-attributes> </region-attributes> </region>
// Configure a partitioned region for heap LRU eviction. The resource manager controls the limits. <region-attributes refid="PARTITION_HEAP_LRU"> </region-attributes>
Region currRegion = cache.createRegionFactory() .setEvictionAttributes(EvictionAttributes.createLRUHeapAttributes(EvictionAction.LOCAL_DESTROY)) .create("root");