Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-75919

Investigate if runTransactionOnShardingCatalog should always use cluster transaction API

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.1.0-rc0, 7.0.0-rc1
    • None
    • None
    • None
    • Fully Compatible
    • v7.0
    • Sharding NYC 2023-04-17, Sharding NYC 2023-05-01

    Description

      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.

      Attachments

        Activity

          People

            jack.mulrow@mongodb.com Jack Mulrow
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: