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

Usability testing for ANSA when shards have an existing incorrect shardIdentity document

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 3.3.14
    • None
    • Sharding
    • None
    • Fully Compatible
    • Sharding 2016-09-19, Sharding 2016-10-10

    Description

      There are two scenarios where an incorrect shardIdentity document can matter.
      1) When adding a new shard, if there is already a shardIdentity document on the shard, and it doesn't match the one that is attempted to be added during the addShard process.

      2) When the shard is already a part of a sharded cluster, but somehow the shardIdentity document is incorrect and doesn't match what is sent by mongos in setShardVersion.

      For both cases we should manually double-check that things fail the way we expect them to, and with reasonable error messages that would be clear to a user and to our support team if a user somehow got themselves into one of those states.

      Attachments

        Activity

          People

            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: