[SERVER-8959] Better story for mongos refresh when another mongos dropped a database Created: 12/Mar/13  Updated: 01/Apr/13  Resolved: 01/Apr/13

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.4.0-rc2
Fix Version/s: None

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

Attachments: File stale_db.js    
Issue Links:
Duplicate
duplicates SERVER-4537 better protect all sharding admin ope... Closed
Related
Operating System: ALL
Participants:

 Description   

Setup: 2 mongos, 1 shard

1. Enable sharding on test db ysing mongos A.
2. Use mongos B to perform a query against test db.
3. Use mongos A to drop test db.
4. Trying to enable sharding with mongos B gives the result:

{ "ok" : 0, "errmsg" : "already enabled" }

Current workaround is to force mongos B to refresh it's config with

{ flushRouterConfig: 1 }

Also attaching script demonstrating the behavior (stale_db.js).



 Comments   
Comment by Eliot Horowitz (Inactive) [ 01/Apr/13 ]

SERVER-4537

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