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

Have Resharding be [RRFaM] aware

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 5.0.4, 5.1.0-rc0
    • None
    • None
    • Fully Compatible
    • v5.0
    • Sharding 2021-08-23, Sharding 2021-09-06, Sharding 2021-09-20
    • 2

    Description

      Documents being resharded have associated config.transactions updates communicated via standard MDB oplog fetching queries. Without RRFaM, the pre/post images for retryable find and modifies are stored in the oplog themselves and captured by these queries.

      With RRFaM, those images are written elsewhere not yet known to resharding. Without any work, resharding while using RRFaM will lose the necessary data for retryable findAndModifies.

      It's safe and correct to document that to reshard a collection, a user must first turn off RRFaM on every node in the sharded cluster prior to issuing a resharding command.

      For this ticket, we aim to do better and have resharding be aware of the config.image_collection data and copy over the necessary items as needed.

      Attachments

        Issue Links

          Activity

            People

              randolph@mongodb.com Randolph Tan
              daniel.gottlieb@mongodb.com Daniel Gottlieb
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: