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

Investigate if it is possible to make resharding generate fewer IncompleteTransactionHistory records

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

      The ReshardingTxnCloner is very conversvative when transferring retryable writes/transaction information from the donor. It just scans through the config.transactions table and convert them to IncompleteTransactionHistory records without attmepting to scan through the oplog history chain. This has a side effect of generating too many IncompleteTransactionHistory records on the recipients even though these transactions/retryable writes were originally from a different namespace.

      This optimization has to also take into account special collections like time series (which has a different namespace name for the bucket collection)

            Assignee:
            Unassigned Unassigned
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: