Loading...

XML

Word

Printable

JSON

The RecipientStateMachine should manage a task executor for the config.transaction instances to be scheduled on. This may most easily be achieved by having the cloneConfigTxnsForResharding() function take a TaskExecutor as part of its input and scheduling tasks on the same ScopedTaskExecutor the RecipientStateMachine instance is running on.

depends on

SERVER-51493 Revisit how config.transactions cloner for resharding blocks thread waiting for outstanding prepared transaction to resolve

is related to

SERVER-52593 Integrate ReshardingOplogFetcher into RecipientStateMachine

SERVER-52594 Integrate ReshardingOplogApplier into RecipientStateMachine

related to

SERVER-54616 Rewrite ReshardingTxnCloner::_updateSessionRecordsUntilPipelineExhausted to not use recursion

SERVER-54626 Retryable writes may execute more than once in resharding if statements straddle the fetchTimestamp

SERVER-54681 Resharding recipient shards which are also donor may fail retryable writes with IncompleteTransactionHistory too early

SERVER-55214 Resharding txn cloner can miss config.transactions entry when fetching

(2 related to)