Summary: The space includes a dedicated thread that is responsible for clearing expired objects.

Overview

The Lease Manager is a special thread inside the space, that is responsible for clearing and invalidating expired objects.

You can control how often this thread invokes the invalidation process. This involves iterating through all the expired space objects since the last invalidation, and allowing the JVM garbage collector to release the memory consumed for the object. When using a persistent space this operation also removes the objects from the database.

To configure the Lease Manager interval use the following:

space-config.lease_manager.expiration_time_interval=10000
  • When writing objects into the space using a short lease time, it is recommended to configure the lease manager interval to be short.
  • The NOTIFY_LEASE_EXPIRATION notification is called when the Lease Manager invalidates the object.
  • Notifications for expired objects sent both from the primary and the backup space (in case you have such).
  • When a transaction is timed out, its locked objects are released when the lease manager thread is triggered. This means that if a client fails while a transaction is opened with locked Entries (take, write, read, and update using transactions), the locked objects are released once the lease manager thread identifies the expired transaction. With transient spaces it happens after 10 seconds, and 60 seconds with persistent spaces.
GigaSpaces.com - Legal Notice - 3rd Party Licenses - Site Map - API Docs - Forum - Downloads - Blog - White Papers - Contact Tech Writing - Gen. by Atlassian Confluence