Relax restrictions for updates to new shard key fields during resharding

XMLWordPrintableJSON

    • Sharding
    • Sharding 2020-12-28, Sharding 2021-01-11, Sharding 2021-01-25
    • 3
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The changes from 6508f5d as part of SERVER-49825 reused the WouldChangeOwningShard error response handling in mongos. This comes with the following limitations:

      • the update must be performed in a batch of size 1
      • the update must be performed as a retryable write or in a multi-document transaction
      • the update must not be performed as a multi=true update (this restriction was omitted from SERVER-49825 and maybe needs to be added)

      One thought would be to have the donor shard handle the WouldChangeOwningShard exception locally without bubbling it up to mongos.

            Assignee:
            [DO NOT USE] Backlog - Sharding Team
            Reporter:
            Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: