jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OAK-3554) Use write concern of w:majority when connected to a replica set
Date Mon, 02 Nov 2015 15:05:27 GMT

     [ https://issues.apache.org/jira/browse/OAK-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Marcel Reutegger updated OAK-3554:
----------------------------------
         Labels: resilience  (was: )
    Component/s: core

> Use write concern of w:majority when connected to a replica set
> ---------------------------------------------------------------
>
>                 Key: OAK-3554
>                 URL: https://issues.apache.org/jira/browse/OAK-3554
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, mongomk
>            Reporter: Chetan Mehrotra
>              Labels: resilience
>             Fix For: 1.3.10
>
>
> Currently while connecting to Mongo MongoDocumentStore relies on default write concern
provided as part of mongouri. 
> Recently some issues were seen where Mongo based Oak was connecting to 3 member replica
set and there were frequent replica state changes due to use of VM for Mongo. This caused
data loss and corruption of data in Oak.
> To avoid such situation Oak should default to write concern of majority by default. If
some write concern is specified as part of mongouri then that should take precedence. This
would allow system admin to take the call of tweaking write concern if required and at same
time allows Oak to use the safe write concern.



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

Mime
View raw message