Ban whole_cluster_metadata_notifications test from running with majority read concern off

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.2.1, 4.3.1
    • Affects Version/s: None
    • Component/s: None
    • Fully Compatible
    • ALL
    • v4.2
    • 12
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When running in a sharded multi-statement transaction passthrough on the majority read concern off variant, if two databases used in whole_cluster_metadata_notifications are on different shards, the test will fail. This is due to SERVER-37559, which rejects multi-shard transactions when enableMajorityReadConcern is false.

            Assignee:
            Davis Haupt (Inactive)
            Reporter:
            Davis Haupt (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: