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

Blacklist out_to_existing.js from sharding_csrs_continuous_config_stepdown

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.1.10
    • None
    • None
    • None
    • Fully Compatible
    • ALL
    • 24

    Description

      As exposed in our testing infrastructure, it seems like a config stepdown can cause a drop collection to be missed by both shards, leaving the cluster in a state where all shards agree the collection is sharded, but mongos knows it is not sharded.

      Attachments

        Activity

          People

            ted.tuckman@mongodb.com Ted Tuckman
            ted.tuckman@mongodb.com Ted Tuckman
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: