You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Marcel Reutegger (Jira)" <ji...@apache.org> on 2020/03/17 12:15:00 UTC

[jira] [Updated] (OAK-6366) Detect unsupported combination of read and write concern

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

Marcel Reutegger updated OAK-6366:
----------------------------------
    Fix Version/s:     (was: 1.26.0)

> Detect unsupported combination of read and write concern
> --------------------------------------------------------
>
>                 Key: OAK-6366
>                 URL: https://issues.apache.org/jira/browse/OAK-6366
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: mongomk
>            Reporter: Marcel Reutegger
>            Priority: Minor
>
> With OAK-4069 Oak will try to use a majority read concern when connected to a replica set. The implementation should be more careful when setting a majority read concern automatically and take the write concern into account. It is currently possible to end up with a system that has a user configured write concern of 1 and a majority read concern. This results in a non-functional system and should be prevented.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)