[SERVER-44122] createIndexes provides incorrect IndexBuildProtocol for two phase index builds Created: 20/Oct/19 Updated: 29/Oct/23 Resolved: 22/Oct/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Benety Goh |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Execution Team 2019-10-21, Execution Team 2019-11-04 |
| Participants: |
| Description |
|
The createIndexes command is currently passing IndexBuildProtocol::kSinglePhase to the IndexBuildsCoordinator when starting index builds. This is currently not an issue for index builds on the primary but will result in unexpected behavior if index builds are allowed to survive stepdowns. We would not get the blocking behavior added in |
| Comments |
| Comment by Githook User [ 21/Oct/19 ] |
|
Author: {'name': 'Benety Goh', 'username': 'benety', 'email': 'benety@mongodb.com'}Message: |