[SERVER-74135] Investigate _signalPrimaryForAbortAndWaitForAbort behaviour on killop Created: 17/Feb/23  Updated: 22/Mar/23  Resolved: 22/Mar/23

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

Type: Improvement Priority: Major - P3
Reporter: Yujin Kang Park Assignee: Josef Ahmad
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-74194 Allow secondaries to cancel index bui... Closed
Assigned Teams:
Storage Execution
Sprint: Execution Team 2023-04-03
Participants:

 Description   

Voting can fail due to killop having killed the opCtx. Behaviour before introducing the voting procedure for aborts was that the secondary node would crash. It would be an improvement if this voting was resilient to killop, and the killop actually aborted the index in all the replset.



 Comments   
Comment by Josef Ahmad [ 22/Mar/23 ]

SERVER-74194 already implemented the ability to abort a two-phase index build on killOp on a secondary member.

Generated at Thu Feb 08 06:26:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.