mreutegg commented on pull request #453:
URL: https://github.com/apache/jackrabbit-oak/pull/453#issuecomment-1008998035
> What I don't understand is whether it fails ("eventually notices") in the
same run or the next.
At some point while running recovery the process may notice that its lease
expired and fail the recovery with an exception. This may happen when the
recovery reads or updates documents and the `LeaseCheckDocumentStoreWrapper`
refuses to perform the operation.
> Also since the 2nd sentence states that it fails on the "next lease
update" - but unclear whether that's triggered by the time-jumped node or by
any other one.
That's indeed confusing. The second sentence is about the impact on the node
that has the correct time. The node with the incorrect time wants to run
recovery on the clusterId of the node with the correct time. At this point the
node with the correct time will observe its entry in the clusterNodes
collection updated by someone else and conclude that its lease must have
expired.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
