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

Update config.transactions less frequently for retryable writes

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Replication

      For every retryable write we update the session entry in config.transactions, this creates long update chains in WT, a large volume of writes to the WT history store, etc. In general we only need the persisted data during startup to reconstruct the in-memory state, so we could persist the data less frequently and reconstruct the missing pieces from the oplog.

      Caveats: resharding relies on point-in-time access to config.transactions, rollback to stable timestamp would also need some changes.

            Assignee:
            Unassigned Unassigned
            Reporter:
            daniel.gomezferro@mongodb.com Daniel Gomez Ferro
            Votes:
            0 Vote for this issue
            Watchers:
            16 Start watching this issue

              Created:
              Updated: