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

Allow renames of time-series collection buckets

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.1.0-rc0, 7.0.0-rc6, 6.0.9
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Server Security
    • Fully Compatible
    • v7.0, v6.3, v6.0
    • Execution Team 2023-05-29, Security 2023-06-12
    • 124

      Mongosync maintains an internal mapping of source & destination collection UUIDs. Because we can’t update that mapping atomically with creating the collection, mongosync does the following:

      • Create the destination collection using a temporary name: mongosync.tmp.$srcUUID
      • Update mongosync’s UUID map.
      • Rename the destination collection (preserving its UUID).

      The rationale is that, if mongosync goes down at any point in the above workflow, the failure is recoverable.

      Time-series collections don’t presently seem to work with this workflow because they can’t be renamed—either the “aggregate” collection (view + bucket) or the internal bucket collection. (We can create & drop buckets directly, but not rename them.)

      If I’m understanding everything about this properly, then, it would seem that mongosync requires some way to rename time-series collections—or at least their buckets—in order to support these collections.

      For C2C’s purposes it should suffice to ensure the user has setUserWriteBlockMode authorization.

            mark.benvenuto@mongodb.com Mark Benvenuto
            felipe.gasper@mongodb.com Felipe Gasper
            0 Vote for this issue
            9 Start watching this issue