Blacklist out_to_existing.js from sharding_csrs_continuous_config_stepdown

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.1.10
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • 24
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Ted Tuckman
            Reporter:
            Ted Tuckman
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: