[
https://issues.apache.org/jira/browse/OAK-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-4757:
----------------------------------
Attachment: OAK-4757.patch
Updated the patch to only reduce the {{maxWaitTime}} for a connection from the
pool to one minute. Setting a socket timeout is in my view not necessarily
helpful, because it will result in an exception even though the operation is
still pending on the MongoDB server. We should revise timeouts when MongoDB
supports a timeout for write operations.
> 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, 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)
