Currently AsyncIndexUpdate creates a checkpoint with a lifetime of 3
years. Post index complete the checkpoint is moved to point to
revision upto which indexing is done and previous checkpoint is
released.
Now if a system is killed when a index update is in progress
particularly in run method
On Wed, Sep 10, 2014 at 1:33 PM, Alex Parvulescu
alex.parvule...@gmail.com wrote:
Second is the worse in my view, the cp get created and referenced with a
life of 3y, but the async gets shut down and doesn't get a chance to
cleanup. This is a node state that will keep the GC from cleaning
