Overview#FLAIM checkpoint brings the on-disk version of the (Typically eDirectory) Data Store to the same coherent state as the in-memory (FLAIM Cache) database.
FLAIM can perform a FLAIM checkpoint during the minimal update activity on the database.
FLAIM checkpoint acquires a lock on the (typically eDirectory) Data Store and performs the maximum amount of possible work until either the FLAIM checkpoint completes or another thread is waiting to update the Data Store.
To prevent the on-disk database from becoming too far out of sync, there are conditions under which a FLAIM checkpoint is forced even if threads are waiting to update the Data Store:
- If the FLAIM checkpoint thread cannot complete a checkpoint within a specified cpinterval (the default is 3 minutes), it is forced and the dirty cache is cleaned.
- If the size of the dirty FLAIM Cache is larger than the maxdirtycache (if set), a FLAIM checkpoint is forced to bring down the dirty FLAIM Cache size to lowdirtycache (if set) or to zero.