[SERVER-23428] If mongos tells a shard about a CSRS config server string (via SSV), the shard should switch to CSRS mode Created: 30/Mar/16 Updated: 25/Jan/17 Resolved: 18/May/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | code-and-test | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Sharding 12 (04/01/16), Sharding 15 (06/03/16) | ||||||||
| Participants: | |||||||||
| Description |
|
If you upgrade from SCCC to CSRS, but the shard doesn't have to talk to the config servers for a long time (because no splits or migrations are happening on that shard), the shard may not discover that the config servers have switched to CSRS mode. This can cause problems if you ever want to retire the last former SCCC config server. We can mitigate this by using SSV from the mongos with a csrs connection string as a signal to the shard to switch to CSRS mode. |
| Comments |
| Comment by Githook User [ 18/May/16 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |
| Comment by Spencer Brody (Inactive) [ 30/Mar/16 ] |
|
Attaching jstest that demonstrates the problem. |