[SERVER-5058] mongos should update config seed based on rs version Created: 23/Feb/12 Updated: 10/Dec/14 Resolved: 02/May/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.0.2 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Randolph Tan |
| Resolution: | Done | Votes: | 0 |
| Labels: | revisit | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||
| Description |
|
EDIT : previous issue resolved in linked ticket. Mongos should be aware of the current replica set config version, and only update the config seed when this rs config version changes. Also, we should track hidden nodes, for better handling of cases when all visible nodes need to be reconfigured. The related bugs The symptoms include:
While there was not a specific fix for the problem in version 2.2, other changes made in 2.2 mean that the issues this ticket is linked to should not occur in 2.2.x. The related bugs, This issue is still open for the completion of the more defensive fix mentioned above. For 2.0.x (< 2.0.8) releases, the workaround is to ensure that you shutdown a node before removing it from a replica set in a sharded environment. Version 2.0.8 includes a fix for |
| Comments |
| Comment by Greg Studer [ 02/May/14 ] |
|
Issue is no longer applicable with replica set monitor changes and current future directions. |
| Comment by Greg Studer [ 19/Nov/12 ] |
|
This ticket now tracks work on a better rs config seed update behavior, though the current behavior is now safe due to the fixing of |
| Comment by Greg Studer [ 24/Feb/12 ] |
|
This is essentially the same issue as |