Currently, runTransactionOnShardingCatalog() will use the clusterRole to decide if the transaction should execute using the local or cluster wide transaction API client. Now that a config server may run shard role operations, we may want the config server to use the remote client for those operations for compatibility. Seemingly all transactions exclusively write to the config server, so this shouldn't impact correctness in the short term, but could be a limitation for future "sharding catalog" transactions.
- is related to
-
SERVER-76368 Allow TransactionRouter on a mongod to early reap retryable sessions
-
- Closed
-
-
-
- Closed
-