[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: |
|
||||||||
| 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 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: |