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

mark shard as state=invalid in config.shards on DuplicateKeyError from shardIdentity upsert

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Sharding
    • Minor Change
    • Sharding 2016-08-29

      And make mongos ignore shards in config.shards that are marked as invalid (maybe don't create a Shard object for them on ShardRegistry::reload())?

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: