[SERVER-45944] disallow downgrade to 4.2 if there is an index build in progress Created: 04/Feb/20 Updated: 29/Oct/23 Resolved: 18/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sara Williamson | Assignee: | Benety Goh |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Execution Team 2020-02-24 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 38 | ||||||||
| Description |
|
Two phase index builds are a 4.4-only feature. We should not allow a FCV downgrade to 4.2 if there are still index builds in progress. This avoids propagating a commitIndexBuild/abortIndexBuild oplog entry to the secondary node if the index builds completes after the FCV update is done. |
| Comments |
| Comment by Githook User [ 18/Feb/20 ] |
|
Author: {'username': 'benety', 'name': 'Benety Goh', 'email': 'benety@mongodb.com'}Message: |
| Comment by Githook User [ 18/Feb/20 ] |
|
Author: {'username': 'benety', 'name': 'Benety Goh', 'email': 'benety@mongodb.com'}Message: create mode 100644 jstests/noPassthrough/index_downgrade_fcv.js |