[
https://issues.apache.org/jira/browse/OAK-9564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17899533#comment-17899533
]
Julian Reschke commented on OAK-9564:
-------------------------------------
trunk: (1.44.0)
[2ebff8f003|https://github.com/apache/jackrabbit-oak/commit/2ebff8f003ca6914d619091ce8fb1d2efa4ede44]
[9b495d9795|https://github.com/apache/jackrabbit-oak/commit/9b495d97959a4dd884e008433b98706e6c409912]
[e1ff20daf5|https://github.com/apache/jackrabbit-oak/commit/e1ff20daf5c962679f47e01831151a6f84777b7f]
[d653908abd|https://github.com/apache/jackrabbit-oak/commit/d653908abd49efb992f9e14fd3593a1e4b049fee]
[01f51d837e|https://github.com/apache/jackrabbit-oak/commit/01f51d837e71978bf27767877a6e14fb56d23189]
> Lease failure when update takes longer than socket timeout
> ----------------------------------------------------------
>
> Key: OAK-9564
> URL: https://issues.apache.org/jira/browse/OAK-9564
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: mongomk
> Reporter: José Andrés Cordero Benítez
> Assignee: Marcel Reutegger
> Priority: Major
> Fix For: 1.44.0
>
>
> The DocumentNodeStore may consider a lease update as failed when the
> operation takes longer than the socket timeout and later succeeds on MongoDB
> within the lease time. In this situation the lease mechanism currently thinks
> there was a lease update from another process and therefore backs off.
> The implementation keeps track of the last successful lease update and based
> on this information performs a conditional lease update. The implementation
> should be more tolerant when it encounters an 'unexpected' update within the
> lease period and still consider the lease valid.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
