-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.4.0-rc2
-
Component/s: Sharding
-
None
-
ALL
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).
- duplicates
-
SERVER-4537 better protect all sharding admin operations from simultaneous commands
- Closed