[SERVER-12688] After a shard is removed, db.collection.stats() still shows the removed shard Created: 12/Feb/14  Updated: 10/Dec/14  Resolved: 18/Feb/14

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 2.4.9, 2.5.5
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Linda Qin Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates SERVER-8059 After movePrimary, db.getCollectionNa... Closed
Operating System: ALL
Participants:

 Description   

Steps to reproduce:

  1. Start a sharded cluster with 2 shards
  2. Shard a collection and insert documents to that collection.
  3. db.collection.stats() shows 2 shards
  4. Connect to a mongos and remove a shard
  5. db.collection.stats() still shows 2 shards
  6. flushRouterConfig fixes the issue. The shard being removed is not showing in the output of db.collection.stats() any more.


 Comments   
Comment by Daniel Pasette (Inactive) [ 18/Feb/14 ]

same root cause as SERVER-8059

Generated at Thu Feb 08 03:29:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.