[SERVER-56767] Check for interrupt before initializing the _tenantOplogApplier Created: 07/May/21  Updated: 29/Oct/23  Resolved: 10/May/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.9.0-rc1, 5.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Lingzhi Deng Assignee: Lingzhi Deng
Resolution: Fixed Votes: 0
Labels: pm-1791_non-cloud-blocking, pm-1791_other_required, post-rc0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Duplicate
is duplicated by SERVER-56178 Investigate oplog batcher during shut... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.9
Sprint: Repl 2021-05-17
Participants:
Linked BF Score: 47

 Description   

_interrupt calls _cancelRemainingWork which would cancel the _tenantOplogApplier if it exists. But I think it is possible for the _tenantOplogApplier to be initialized after _cancelRemainingWork is called. In that case, the _tenantOplogApplier would never be shut down. I think we should check for interrupt before initializing the _tenantOplogApplier.



 Comments   
Comment by Githook User [ 10/May/21 ]

Author:

{'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}

Message: SERVER-56767: Check for interrupt before initializing tenant oplog applier and starting tenant cloners

(cherry picked from commit 5e45283c8c6f191dd0f301808942e0f11e307ff5)
Branch: v4.9
https://github.com/mongodb/mongo/commit/084572422d66ed815bddd792af40698eaafa2b7c

Comment by Githook User [ 10/May/21 ]

Author:

{'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}

Message: SERVER-56767: Check for interrupt before initializing tenant oplog applier and starting tenant cloners
Branch: master
https://github.com/mongodb/mongo/commit/5e45283c8c6f191dd0f301808942e0f11e307ff5

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