OPERATIONAL DEFECT DATABASE
...
...
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.
Click on a version to see all relevant bugs
MongoDB Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
