jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From José Andrés Cordero Benítez (Jira) <j...@apache.org>
Subject [jira] [Commented] (OAK-9564) Lease failure when update takes longer than socket timeout
Date Fri, 03 Sep 2021 10:42:00 GMT

    [ https://issues.apache.org/jira/browse/OAK-9564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409428#comment-17409428
] 

José Andrés Cordero Benítez commented on OAK-9564:
--------------------------------------------------

I will submit a test to reproduce this issue and a patch to solve it soon.

> 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
>            Priority: Major
>
> 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.3.4#803005)

Mime
View raw message