[SERVER-38701] Prohibit new simultaneous index builds oplog entries in applyOps Created: 19/Dec/18 Updated: 29/Oct/23 Resolved: 06/Feb/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.8 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Louis Williams |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | index-repl | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Storage NYC 2019-02-11 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
startIndexBuild, abortIndexBuild and commitIndexBuild will return errors when called through applyOps. |
| Comments |
| Comment by Githook User [ 06/Feb/19 ] |
|
Author: {'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}Message: |
| Comment by Dianna Hohensee (Inactive) [ 05/Feb/19 ] |
|
Pulling this ticket forward because we're concerned what mischief the fuzzer could cause by calling the new oplog entries via applyOps, once we have |