ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.1.0-rc0, 9.1.0-rc1026
    • Affects Version/s: None
    • Component/s: None
    • None
    • DB Integration & Observability
    • Fully Compatible
    • QE 2026-10-26, QE 2026-11-23
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When building the metadata for a commitTransaction command, we currently repeat the shardId values verbatim in all sets, e.g.

      {
        collectionParticipants: {"testDB.testColl": ["shardA", "shardB"]},
        databaseParticipants: {"testDB": ["shardA", "shardB"]},
        clusterParticipants: ["shardA", "shardB"]
      }
      

      ShardIds are typically 20 bytes long on Atlas.
      Interning the shardId strings and only storing a positional index can reduce the storage and wire-transfer size, e.g.

      {
        shardIds: ["shardA", "shardB"],
        collectionParticipants: {"testDB.testColl": [0, 1]},
        databaseParticipants: {"testDB": [0, 1]},
        clusterParticipants: [0, 1]
      }
      

      Investigate this interning as a potential performance improvement.

      As part of this effort, we should also investigate shortening the verbose field names inside the structure so that they become single letter field names. This is the pattern the rest of the oplog uses.

            Assignee:
            Lyublena Antova
            Reporter:
            Jan Steemann
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: