Question regarding missing _lastRev recovery - OAK-1295

2014-04-02 Thread Amit Jain
Hi, How do we expose _lastRev recovery operation? This would need to check all the cluster nodes info and run recovery for those nodes which need recovery. 1. We either have a scheduled job which checks all the nodes and run the recovery. What should be the interval to trigger the job? 2. Or if

RE: Question regarding missing _lastRev recovery - OAK-1295

2014-04-02 Thread Marcel Reutegger
Hi, I think the recovery should be triggered automatically by the system when: 1) a cluster node starts up and sees it didn't shut down properly. I'm not sure this information is available, but remember we discussed this once. 2) a cluster node sees a lease timeout of another cluster node and

Re: Question regarding missing _lastRev recovery - OAK-1295

2014-04-02 Thread Amit Jain
Hi, 1) a cluster node starts up and sees it didn't shut down properly. I'm not sure this information is available, but remember we discussed this once. Yes, this case has been taken care of in the startup. this check could be done in the background operations thread on a regular basis.

Re: Question regarding missing _lastRev recovery - OAK-1295

2014-04-02 Thread Chetan Mehrotra
The lease time is set to 1 minute. Would it be ok to check this every minute, from every node? Adding to that the default time intervals are - asyncDelay = 1 sec - The background operation are performed every 1 sec per cluster node. If nothing changes we would fire 1query/sec/cluster node to