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

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 6.0.0-rc0
    • None
    • None
    • Fully Compatible
    • Sharding NYC 2022-03-21, Sharding NYC 2022-04-04
    • 156

    Description

      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.

      Attachments

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: