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

Set shard marked as outstanding as recovery shard if recovery shard not yet chosen

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0, 8.0.0-rc2
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Cluster Scalability
    • Fully Compatible
    • ALL
    • v8.0
    • Cluster Scalability 2024-4-15, Cluster Scalability 2024-4-29

      If a transaction router receives a response without a readOnly value for an added participant, but it previously had that shard marked as readOnly, we mark the shard as "outstanding". The transaction router will treat this shard as a write shard at commit time to avoid accidentally choosing a read-optimized commit when it should not. It's possible that this shard is the only shard treated as a write shard in the commit protocol, and if so would be expected to be chosen as the recovery shard - the transaction router should pick a shard it is marking as 'outstanding' as the recovery shard if one has not yet been chosen for the transaction.

            Assignee:
            janna.golden@mongodb.com Janna Golden
            Reporter:
            janna.golden@mongodb.com Janna Golden
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: