[SERVER-25276] Remove code for parsing and handling config server connection string during sharding state recovery Created: 25/Jul/16 Updated: 28/Mar/18 Resolved: 08/Dec/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Kaitlin Mahar |
| Resolution: | Done | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Sprint: | Sharding 2017-01-02, Sharding 2017-12-18 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
In 3.4 we stop writing the shardId and config server connection string to the minOpTimeRecovery document, as that information is redundant of information present in the shardIdentity document. We still handle reading that information, however, to handle backwards compatibility during upgrade from 3.2 to 3.4. During the 3.6 dev cycle this can be removed. |
| Comments |
| Comment by Githook User [ 28/Mar/18 ] |
|
Author: {'email': 'jack.mulrow@mongodb.com', 'name': 'Jack Mulrow', 'username': 'jsmulrow'}Message: |
| Comment by Githook User [ 08/Dec/17 ] |
|
Author: {'name': 'Kaitlin Mahar', 'email': 'kaitlin.mahar@mongodb.com', 'username': 'kmahar'}Message: |
| Comment by Dianna Hohensee (Inactive) [ 27/Sep/17 ] |
|
Re-opening, as |
| Comment by Esha Maharishi (Inactive) [ 10/Jan/17 ] |
|
Will be done as part of |