[jira] [Commented] (OAK-3554) Use write concern of w:majority when connected to a replica set

["Chetan Mehrotra (JIRA)" <ji...@apache.org>]

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

Chetan Mehrotra commented on OAK-3554:
--------------------------------------

Due to OAK-2592 even setting the write concern would not be effective in all cases but chances of corruption would be reduced. So it would be good to have this change done in parallel to OAK-2592

> 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: mongomk
>            Reporter: Chetan Mehrotra
>             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)