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 "Davide Giannella (JIRA)" <ji...@apache.org> on 2019/04/09 10:37:11 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 ]

Davide Giannella updated OAK-6366:
----------------------------------
    Fix Version/s: 1.14.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
>             Fix For: 1.12.0, 1.14.0
>
>
> 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
(v7.6.3#76005)