OplogWriter should not hold on to session through rollbacks

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Critical - P2
    • None
    • Affects Version/s: 8.0.13
    • Component/s: None
    • None
    • Replication
    • ALL
    • Repl 2025-09-29
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The OplogWriterImpl holds on to an OperationContext throughout its lifetime, and this OperationContext will have a session after the first write is done. If a rollback occurs, that WT's session cache will have a stale epoch, and any future cursors from it will be leaked.

            Assignee:
            Joseph Obaraye
            Reporter:
            Matthew Russotto
            Votes:
            0 Vote for this issue
            Watchers:
            16 Start watching this issue

              Created:
              Updated: