[ https://issues.apache.org/jira/browse/OAK-9564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471875#comment-17471875 ]
Marcel Reutegger edited comment on OAK-9564 at 1/10/22, 12:15 PM: ------------------------------------------------------------------ Created and merged https://github.com/apache/jackrabbit-oak/pull/455 to revert the changes. was (Author: mreutegg): Created https://github.com/apache/jackrabbit-oak/pull/455 to revert the changes. > 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.1#820001)