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 "Julian Reschke (JIRA)" <ji...@apache.org> on 2019/05/16 07:01:00 UTC

[jira] [Commented] (OAK-7543) MissingLastRevSeekerTest fails on MongoDB with secondary preferred

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

Julian Reschke commented on OAK-7543:
-------------------------------------

 [^OAK-7543-1.8.diff] - proposed backport to 1.8

> MissingLastRevSeekerTest fails on MongoDB with secondary preferred
> ------------------------------------------------------------------
>
>                 Key: OAK-7543
>                 URL: https://issues.apache.org/jira/browse/OAK-7543
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: documentmk, mongomk
>    Affects Versions: 1.9.3
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Minor
>              Labels: candidate_oak_1_8
>             Fix For: 1.10.0, 1.9.4
>
>         Attachments: OAK-7543-1.8.diff
>
>
> MissingLastRevSeekerTest actually does not run on MongoDB right now, but changing the test accordingly revealed an issue with the MongoDB specific implementation of MissingLastRevSeeker when running on a replica-set and secondary preferred read preference.
> The class MongoMissingLastRevSeeker uses the configured read preference when checking for cluster node info entries that require recovery. This is inconsistent because the candidate nodes are read with primary read preference.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)