Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-42419

Ban whole_cluster_metadata_notifications test from running with majority read concern off

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

      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@mongodb.com Davis Haupt (Inactive)
            Reporter:
            davis.haupt@mongodb.com Davis Haupt (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: