-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Cluster Scalability
-
Fully Compatible
-
ALL
-
Cluster Scalability 2024-4-1
-
8
-
3
This causes the prevOpTime chain to grow and for reloading the prevOpTime chain from disk following a primary failover to take nominally longer. In extreme cases of repeated primary failovers seen in testing on slower build variants, this can prevent the ReshardingTxnCloner from making forward progress.
We can skip calling resharding::data_copy::updateSessionRecord(TransactionParticipant::kDeadEndSentinel) when TransactionParticipant::hasIncompleteHistory() == true.
- is related to
-
SERVER-87723 Consider also removing config.transactions entries in CleanupConcurrencyWorkloads
- Closed