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

Unset default read concern at end of read_write_concern_defaults_startup.js

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.4
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Sharding 2020-02-10
    • 50

      This test sets the default read concern to majority which causes the ShardingTest index consistency shutdown hook to use majority read concern for an aggregation, triggering a failure when majority read concern is disabled. The test should unset the default before shutting down to avoid this.

            Assignee:
            jack.mulrow@mongodb.com Jack Mulrow
            Reporter:
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: