Info

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.

Top User Comments

xgen-internal-githook commented on Tue, 26 Mar 2024 01:22:15 +0000: Author: {'name': 'Brett Nawrocki', 'email': 'brett.nawrocki@mongodb.com', 'username': 'brettnawrocki'} Message: SERVER-87307 ReshardingTxnCloner marks $incompleteOplogHistory once GitOrigin-RevId: d3c4b7f930b0e18febb4cb0e52124d1576d4483e Branch: master https://github.com/mongodb/mongo/commit/975a704beff870945c4d8677850776f413e9e6cd

Steps to Reproduce