[SERVER-47536] Investigate behavior of sending a killop to an index builder thread and state transitions Created: 14/Apr/20  Updated: 29/Oct/23  Resolved: 04/Jun/20

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

Type: Improvement Priority: Major - P3
Reporter: Louis Williams Assignee: Gregory Wlodarek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2020-05-04, Execution Team 2020-06-01, Execution Team 2020-06-15
Participants:

 Description   

After SERVER-46560, the index builder thread is interruptible. While this is useful for cancelling the createIndexes command thread or using dropIndexes to abort an active index build, this opens the possibility for users to interrupt an internal thread.

The behavior under normal circumstances is that the index builder will corrrectly-self destruct and clean up, however we should investigate what happens when a node step-down interleaves with this operation.



 Comments   
Comment by Githook User [ 04/Jun/20 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-47536 Test the behaviour of sending a killOp to an index builder thread while stepping down
Branch: master
https://github.com/mongodb/mongo/commit/3b8ba036f2d553c9e15528fa6f7badf533e28e2a

Comment by Githook User [ 04/Jun/20 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-47536 Test the behaviour of sending a killOp to an index builder thread while stepping up
Branch: master
https://github.com/mongodb/mongo/commit/87be41e2f338f45cb1b34ae8042d489d6ce9c3cd

Comment by Louis Williams [ 14/Apr/20 ]

I have a suspicion (and hope) that the resulting behavior ends up like this test where sending a killop to the index builder thread on a secondary crashes the server and the node must restart. We should explore if there is a cleaner way to do this.

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