[SERVER-4162] refactor of stale config logic Created: 27/Oct/11 Updated: 28/Oct/11 Resolved: 28/Oct/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Need to better define where stale config exceptions may happen, and catch them appropriately. In particular, we probably do not need to throw SCEs on the mongos side unless recv'd from mongod, if we detect a stale config on a mongos node we should simply fix and continue. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 28/Oct/11 ] |
|
as per discussion, has to go back to top to re-do shard list |