[
https://issues.apache.org/jira/browse/OAK-6366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16053617#comment-16053617
]
Marcel Reutegger commented on OAK-6366:
---------------------------------------
Either the system should refuse to start with this configuration or fall back
to a local read concern. I slightly prefer the first because the fallback isn't
a recommended configuration.
> 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.8
>
>
> 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
(v6.4.14#64029)
