[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: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Setup: 2 mongos, 1 shard 1. Enable sharding on test db ysing mongos A.
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 ] |