[SERVER-54168] Possible runaway tenant migration thread running TenantOplogBatcher Created: 01/Feb/21  Updated: 29/Oct/23  Resolved: 09/Feb/21

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

Type: Bug Priority: Major - P3
Reporter: Vishnu Kaushik Assignee: Lingzhi Deng
Resolution: Fixed Votes: 0
Labels: pm-1791_other_required
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-53023 Create TTL index on config.tenantMigr... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2021-02-08, Repl 2021-02-22
Participants:

 Description   

A bug was exposed while working on SERVER-53023 (creating the TTL index on the recipient).

When we viewed the logs for a failing test after the TTL index ticket changes were made, we saw that a few tenant migrations were started, and each of these completed as well (we saw a "Starting tenant migration ..." and "Marked.." pair for each MigrationID). However, even after the last migration had completed, we found that the OplogBatcher was still running.

Maybe this is because the TenantOplogBatcher is not being joined in the TenantOplogApplier's destructor, for example.



 Comments   
Comment by Githook User [ 09/Feb/21 ]

Author:

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

Message: SERVER-54168: TenantOplogApplier should join TenantOplogBatcher
Branch: master
https://github.com/mongodb/mongo/commit/dd02d9c22485828515941f2b18d37115c72fd8df

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