Summary: The ALL_IN_CACHE Cache policy

Overview

When running in ALL_IN_CACHE cache policy mode, the space only uses the available physical memory. When running in a persistent space mode and having the External Data Source defined, the space data is backed with the underlying database, but the overall capacity of the space does not exceed the capacity of the available physical memory.

When using the All IN CACHE, the cache size parameter is ignored.

SpaceMemoryShortageException

The SpaceMemoryShortageException is thrown when:

  • The utilized memory is above the space-config.engine.memory_usage.high_watermark_percentage threshold.
  • The utilized memory is above the space-config.engine.memory_usage.write_only_block_percentage threshold and a write-type operation has been called.

    The SpaceMemoryShortageException or MemoryShortageException includes information about:

  • The space host name
  • The space container name
  • The space name
  • The total available memory
  • The total used memory

Here is an example of the org.openspaces.core.SpaceMemoryShortageException message:

SpaceMemoryShortageException at: host: MachineHostName, container: mySpace_container1_1, space mySpace, 
total memory: 1820 mb, used memory: 1283 mb

Getting a SpaceMemoryShortageException when running in ALL-IN_CACHE policy mode, alerts us that the heap size allocated for the VM is too low, or the garbage collection settings are not tuned correctly. You should consider increasing the VM heap size or move into more advanced garbage collector.

When running with a large heap size you should tune the memory manager settings. This will avoid throwing SpaceMemoryShortageException too early. See the Handling Large JVM Heap Size section for details.

GigaSpaces.com - Legal Notice - 3rd Party Licenses - Site Map - API Docs - Forum - Downloads - Blog - White Papers - Contact Tech Writing - Gen. by Atlassian Confluence