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

Add feature flag just for using txn API for updating document shard key value

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Sharding NYC 2022-03-21, Sharding NYC 2022-04-04
    • 156

      As of SERVER-59186, we use the internal transaction API for updates that change a document's shard key value and cause it to move shards. That behavior is guarded by the feature flag for PM-2210 (here and here). The performance of the transaction API path is worse than the original implementation, so we should add a new feature flag just to guard that path so we have more time to investigate and can still enable the API for 6.0 projects that need it.

            Assignee:
            sanika.phanse@mongodb.com Sanika Phanse (Inactive)
            Reporter:
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: