Overview#FLAIM checkpoint is a Process that 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 DIB 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.
cpinterval is the time for which the database waits before it initiates the FLAIM checkpoint NDS Thread which brings the on-disk version of the database up to the same coherent state as the in-memory (cache) database. The checkPointThread flushes the Dirty cache to the Disk partition, followed by cleaning up the Roll-Forward Log.
- If the checkPointThread 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 (default is zero).