[SERVER-39525] Move the IndexBuildsCoordinator::shutdown() call so that it does not conflict with the ReplicationStateTransitionLockGuard used in server shutdown Created: 12/Feb/19  Updated: 29/Oct/23  Resolved: 26/Feb/19

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

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

Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2019-02-25, Storage NYC 2019-03-11
Participants:

 Comments   
Comment by Githook User [ 26/Feb/19 ]

Author:

{'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@10gen.com', 'username': 'DiannaHohensee'}

Message: SERVER-39525 move IndexBuildsCoordinator::shutdown() outside the RSTL lock, but still after setKillAllOperations()
Branch: master
https://github.com/mongodb/mongo/commit/1ba2e45711fb15801539d0bec022a2a474155c09

Comment by Dianna Hohensee (Inactive) [ 15/Feb/19 ]

Eric thinks that the general signal to all opCtx that they are interrupted may do all the work for us, no need to interrupt index builds actively.

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