[SERVER-38702] Set up FCV for simultaneous index builds Created: 19/Dec/18 Updated: 06/Dec/22 Resolved: 23/Sep/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
FCV 4.0 should perform v4.0 single-phase index builds. FCV 4.2 should execute two-phase index builds across a replica set. This ticket should be done after:
createIndexes oplog entries via applyOps should be protected against? Index builds that begin in FCV 4.0, in order to parallel v4.0 index builds, should be aborted on primary stepdown and should not be recovered on start up if begun on a primary. Furthermore, consider whether any special handling of the behavior in Lastly, |
| Comments |
| Comment by Benety Goh [ 23/Sep/19 ] |
|
FCV constants are available in |