On 14/01/16 18:34, "Julian Reschke" <[email protected]> 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 in trunk, see r1695671 (might be only on startup, >though). The current model is that at startup this is enforced, but at runtime this is not enforced at the oak level. What we currently have is a JMX method which should be hooked into some sort of runtime monitoring (be that external or internal eg via health checks). Such a runtime monitoring would not be enough though as it would certainly not react fast enough. So if we're saying we need clocks to be in sync at any given time, we probably have to combine checking clocks upon every lease update, as well as restricting valid revisions to be within the lease window. Cheers, Stefan
