[jira] [Commented] (OAK-2058) Hard-coded write concern

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

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

Chetan Mehrotra commented on OAK-2058:
--------------------------------------

[~mreutegg] Those hardcoded concerns are intentional and were done as part of OAK-1645. Reasoning being that we set the right concern where we deem its required. For example while reading the root revision we use the preference to Primary. For code flows where we can read from secondaries we do not explicitly specify any preference and rely on the user specifying the perference.

So per default setup all code paths would use readPreference Primary. And if the user sets the readPreference to say nearest then also Oak would work fine as it would use the default where its safe to read from secondary and still read from primary for critical paths

> Hard-coded write concern
> ------------------------
>
>                 Key: OAK-2058
>                 URL: https://issues.apache.org/jira/browse/OAK-2058
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core, mongomk
>    Affects Versions: 1.0
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Minor
>             Fix For: 1.1
>
>
> There are some hard-coded write concerns in MongoDocumentStore. This overrides the default write concern of the MongoDB Java driver or the dynamic write concern mechanism we built in Oak (OAK-759). The hard-coded write concerns date back to when the default was UNACKNOWLEDGED. Starting with version 2.10.0 of the Java Driver the default is now ACKNOWLEDGED (aka SAFE).



--
This message was sent by Atlassian JIRA
(v6.2#6252)