The recipient could hit this uassert if the retryable write statement was first started on the recipient set and the same tenant migrates back in after being migrated out (i.e. rs1->rs0->rs1 where rs1 is the recipient set). In that case, the in-memory txnParticipant is still valid and may still have the statement ids recorded from the first time when the retryable writes started.
- is depended on by
-
SERVER-52713 [testing] Add stepdown/kill/terminate to tenant_migration_jscore_passthrough
-
- Closed
-
- related to
-
SERVER-55357 Repeated retryable write execution on tenant migration recipient
-
- Closed
-