[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:
Depends
depends on SERVER-38605 IndexBuildsCoordinator writes commitI... Closed
is depended on by SERVER-39068 Replication of simultaneous index bui... Closed
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: SERVER-38701 Prohibit two phase index build oplog entries through applyOps
Branch: master
https://github.com/mongodb/mongo/commit/12218851055007ca0074301745e4c4f751984d24

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 SERVER-39068 in to start doing an action on receipt of the new oplog entries.

Generated at Thu Feb 08 04:49:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.