[
https://issues.apache.org/jira/browse/OAK-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132346#comment-15132346
]
Stefan Egli commented on OAK-3236:
----------------------------------
different levels where clock drifts have an influence, and should thus be
tested:
* within DocumentNodeStore itself - ie in the revision/conflict-handling
mechanisms
* within the discovery logic - due to the fact that pseudo-network partitioning
can occur under such a scenario
* consequently with TopologyEventListeners that could do leader-dependent
activity *after* a lease end, thus *while* another instance might already have
taken over leadership
> integration test that simulates influence of clock drift
> --------------------------------------------------------
>
> Key: OAK-3236
> URL: https://issues.apache.org/jira/browse/OAK-3236
> Project: Jackrabbit Oak
> Issue Type: Test
> Components: core
> Affects Versions: 1.3.4
> Reporter: Stefan Egli
> Assignee: Stefan Egli
> Fix For: 1.4
>
>
> Spin-off of OAK-2739 [of this
> comment|https://issues.apache.org/jira/browse/OAK-2739?focusedCommentId=14693398&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14693398]
> - ie there should be an integration test that show cases the issues with
> clock drift and why it is a good idea to have a lease-check (that refuses to
> let the document store be used any further once the lease times out locally)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
