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

removeShard returns ShardNotFound if step-up/step-down occurs

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • 3.5.12
    • Sharding
    • None
    • Sharding
    • ALL
    • Sharding 2017-09-11

    Description

      When removeShard is called during a step-up/step-down, the primary config node could finish removing the shard, but not return the response.

      In this case, the next time removeShard is called, the new primary config node will return ShardNotFound instead of DrainingStatus::Completed, since the shard has already been removed.

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            hugh.han Hugh Han
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: