[jira] [Commented] (OAK-4757) Adjust default timeout values for MongoDocumentStore

["Marcel Reutegger (JIRA)" <ji...@apache.org>]

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

Marcel Reutegger commented on OAK-4757:
---------------------------------------

Adjusting {{socketTimeout}} may actually be problematic. The default is *no* timeout. If we change the timeout to e.g. one minute and the operation reaches the server but is blocked because it is waiting for locks, MongoDocumentStore will get an exception and consider the operation as failed even though it is still 'running' on the server. We'd need an operation timeout similar to the query {{maxTime}}. It would be the responsibility of the MongoDB server to cancel long running operations. 
A feature request like this is indeed pending: [SERVER-13622|https://jira.mongodb.org/browse/SERVER-13622].

> Adjust default timeout values for MongoDocumentStore
> ----------------------------------------------------
>
>                 Key: OAK-4757
>                 URL: https://issues.apache.org/jira/browse/OAK-4757
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, mongomk
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Minor
>              Labels: resilience
>             Fix For: 1.6
>
>         Attachments: OAK-4757.patch
>
>
> Some default values timeouts of the MongoDB Java driver do not work well with the lease time we use in Oak.
> Per default there is no socket timeout set and the driver waits for a new connection up to 120 seconds, which is too log for lease update operations. 
> See also OAK-4739.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)