-
Type: Bug
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Serverless
-
ALL
-
Server Serverless 2021-11-01, Server Serverless 2021-11-15, Server Serverless 2021-11-29, Server Serverless 2021-12-13, Server Serverless 2021-12-27, Server Serverless 2022-01-10, Server Serverless 2022-11-28
-
0
stepDown thread: Holding RSTL, blocked on TenantMigrationRecipientService::Instance mutex via interrupt
recipientService thread: Holding TenantMigrationRecipientService::Instance mutex, blocked on RSTL via TenantOplogBatcher->startup() and the opCtx wasn't interrupted because the PrimaryOnlyService interrupts instances first before killing opCtxs.
We should also confirm that we don’t have a similar deadlock pattern elsewhere in the tenant migration donor or recipient code when making op ctx under a mutex.
- related to
-
SERVER-71207 Lock ordering violation between POS mutex lock and instance mutex lock
- Open
-
SERVER-53996 Recipient should not do reads/writes while holding the instance mutex
- Closed
-
SERVER-52723 Handle oplog application restart in TenantMigrationRecipientService
- Closed