> That would be a bug. As part of the recovery for CN2, its _lastRev entry > will be updated to reflect the /tree/node2 change. Let's say previously it > was r7-0-2 and after the recovery is r9-0-2. The current > checkpoint for the async index update on CN1 does not yet see the updated > _lastRev. E.g. it could be at r10-0-1,r7-0-2. On the next index update > (after the recovery), the head revision used to compare against the > checkpoint will be r10-0-1,r9-0-2. Now CN1 will update the index with > changed that happened between r7-0-2 and r9-0-2. > Oh, yes. You're right. I was investigating some issue where last rev update were lost (still haven't gotten around to see why recovery didn't work). But that led my thoughts astray. Would write a test and validate - I still have a bit of nagging feeling.
Thanks, Vikas
