Re: [DISCUSS] avoid bad commits with mis-behaving clock

On 14/01/16 18:34, "Julian Reschke" wrote: >On 2016-01-14 17:36, Vikas Saurabh wrote: >>@Julian, if I understand correctly, OAK-2682 currently is about >> warning, right? It mentions a self-desctruct option but I think it >> wasn't implemented. > >It is implemented

Re: [DISCUSS] avoid bad commits with mis-behaving clock

On 2016-01-14 17:36, Vikas Saurabh wrote: Opened OAK-3883 for this. Have added following: * We can start self-destrucut mode while updating lease * Revision creation should check that newly created revision isn't beyond leaseEnd time * Implementation done for OAK-2682 might be useful to

Re: [DISCUSS] avoid bad commits with mis-behaving clock

Hi, On 14/01/16 01:26, "Vikas Saurabh" wrote: >There's a bit of respite on trunk (due to [1] and friends) and a >sequence of events like {{t1 -> update lease}}, {{t2=t1+7.5hrs -> >commit}} would lead to a shutdown as a big jump like 7.5 hours would >be beyond lease end time. BUT, if there's lease

Re: [DISCUSS] avoid bad commits with mis-behaving clock

Opened OAK-3883 for this. Have added following: * We can start self-destrucut mode while updating lease * Revision creation should check that newly created revision isn't beyond leaseEnd time * Implementation done for OAK-2682 might be useful to summarize suggestions from this thread. @Julian, if

Re: [DISCUSS] avoid bad commits with mis-behaving clock

On 2016-01-14 01:26, Vikas Saurabh wrote: ... Note that in trunk, we also have mechanism to detect misbehaving system clocks; see . Best regards, Julian

[DISCUSS] avoid bad commits with mis-behaving clock

Hi, Recently, in on one of our 3-node clusters, system clock on one server instance jumped ahead by 7.5 hours. The cluster is setup on OAK-1.0.22 so it had features which stall background read (OAK-3388 [0]) if repository seems to be ahead in time. But, it doesn't have lease check feature in