[SERVER-21995] Queries against sharded collections fail after upgrade to CSRS due to caching of config server string in setShardVersion Created: 22/Dec/15 Updated: 25/Jan/17 Resolved: 07/Jan/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.3, 3.3.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | code-and-test, csrsupgrade | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Completed: | |||||||||
| Sprint: | Sharding E (01/08/16) | ||||||||
| Participants: | |||||||||
| Description |
|
setShardVersion caches the config server connection string, and errors if it receives a connection string different than what it expects. This means that if a shard primary is sharding aware with an SCCC setup, then the cluster is upgraded to using CSRS, any future sharding operations that need to run setShardVersion will fail due to the cached config server string not matching. |
| Comments |
| Comment by Githook User [ 14/Jan/16 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: (cherry picked from commit eb140e730ffdcf99f26d9f215dd4391b8978acc9) |
| Comment by Githook User [ 07/Jan/16 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |