[SERVER-49913] Explicitly ignore startIndexBuild and abortIndexBuild oplog entries Created: 25/Jul/20  Updated: 06/Dec/22  Resolved: 21/Nov/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Max Hirschhorn Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Do Votes: 0
Labels: PM-234-M4, PM-234-T-oplog-apply
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding
Participants:

 Description   

startIndexBuild and abortIndexBuild oplog entries are not unexpected oplog entries where we'd want to have resharding's oplog application error.



 Comments   
Comment by Max Hirschhorn [ 21/Nov/20 ]

Recipient shards shouldn't see startIndexBuild or abortIndexBuild oplog entries with us doing SERVER-52771 and SERVER-52772 instead. They'll instead be treated as an error as part of SERVER-49909.

Generated at Thu Feb 08 05:21:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.