[SERVER-31208] FCV needs to durably store whether upgrade/downgrade is in process Created: 21/Sep/17 Updated: 22/Sep/17 Resolved: 22/Sep/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding, Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Geert Bosch | Assignee: | Louis Williams |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Storage 2017-10-02 | ||||||||
| Participants: | |||||||||
| Description |
|
For sharding upgrade/downgrade a targetVersion document needs to be persisted at the points we set the internal schema version. On successful upgrade/downgrade this targetVersion document must be removed again. As this requires changing the parser for setFeatureCompatibilityVersion, this would be a good time to use IDL for the command, assuming that's straightforward to do and doesn't add too much complexity. |
| Comments |
| Comment by Esha Maharishi (Inactive) [ 21/Sep/17 ] |
|
Note that the config server will set targetVersion before its schema has begun being upgrade/downgraded. This will be done under |