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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.3.4
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Sharding 2020-02-10
    • Linked BF Score:
      50

      Description

      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.

        Attachments

          Activity

            People

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

              Dates

              Created:
              Updated:
              Resolved: