[SERVER-75352] Make OplogBatcher's ReplBatcher thread unkillable Created: 27/Mar/23  Updated: 27/Oct/23  Resolved: 03/Apr/23

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

Type: Bug Priority: Major - P3
Reporter: Vishnu Kaushik Assignee: Vishnu Kaushik
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Problem/Incident
is caused by SERVER-70127 Default system operations to be killa... Closed
Sprint: Repl 2023-04-03, Repl 2023-04-17
Participants:
Linked BF Score: 135

 Description   

In SERVER-70127 the default for threads was changed from unkillable to killable. Threads that needed to stay unkillable were supposed to be marked as such. However it seems that the ReplBatcher thread was missed.



 Comments   
Comment by Vishnu Kaushik [ 03/Apr/23 ]

Now that the change in SERVER-70217 has been reverted this has gone away.

Comment by Githook User [ 30/Mar/23 ]

Author:

{'name': 'Jiawei Yang', 'email': 'jiawei.yang@mongodb.com', 'username': 'YoungYang0820'}

Message: Revert "SERVER-70127 change system operation threads to be killable by default"

This reverts commit 9f2867c9da77e2d64df3852f7d4578f10e6f0817.

Revert "SERVER-75352 OplogBatcher's ReplBatcher thread should be unkillable"

This reverts commit 26266d5b736f90961a328399dea5d299cd407ab2.
Branch: master
https://github.com/mongodb/mongo/commit/b5f1d6bb8c06742cde53f028fd266eff584a2537

Comment by Githook User [ 28/Mar/23 ]

Author:

{'name': 'kauboy26', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'}

Message: SERVER-75352 OplogBatcher's ReplBatcher thread should be unkillable
Branch: master
https://github.com/mongodb/mongo/commit/26266d5b736f90961a328399dea5d299cd407ab2

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