[SERVER-39462] Enhance index build logic on secondaries (for simul index builds) to abort early when signaled by an abortIndexBuild oplog entry Created: 08/Feb/19  Updated: 09/Sep/19  Resolved: 09/Sep/19

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

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Benety Goh
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-39239 Two-phase index builds on secondaries... Closed
Duplicate
duplicates SERVER-41870 Implement IndexBuildsCoordinator::abo... Closed
Related
is related to SERVER-39067 Implement new simultaneous index buil... Closed
is related to SERVER-41870 Implement IndexBuildsCoordinator::abo... Closed
Sprint: Storage NYC 2019-03-11, Execution Team 2019-09-09
Participants:

 Description   

This task depends on simplified work added in SERVER-39239, where index builds will only check for abort/commit on reaching a waiting loop for commitIndexBuild/abortIndexBuild oplog entry signals. This task is to check for abort signals more frequently, so an index build doesn't mostly complete before seeing that it was aborted a long time ago – which will hold up replication oplog application the whole while.



 Comments   
Comment by Benety Goh [ 09/Sep/19 ]

SERVER-41870 enabled active index builds, building on prior work in SERVER-39067, to be notified when an abortIndexBuild is processed on a secondary node. No further work to be done for this ticket.

Comment by Benety Goh [ 09/Sep/19 ]

The abort functionality was implemented in SERVER-41870 to signal the index build to stop.

Comment by Benety Goh [ 09/Sep/19 ]

The secondary oplog application logic was updated in SERVER-39067 to call into the IndexBuildsCoordinator to abort the index build.

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