Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Affects versions: None
    • Fix versions: 12.3
    • Platform:
      All
    • Acceptance Test:
      Hide
      RedoLogCompactionAllPersistentTest
      RedoLogCompactionAllTransientTest
      RedoLogCompactionBasicTest
      RedoLogCompactionManyTransientPacketsTest
      RedoLogCompactionMirrorAndLocalViewTest
      RedoLogCompactionTakeMultipleTest
      RedoLogCompactionSkipAllPersistentRangesOptimizationTest
      RedoLogTxnCompactionBasicTest
      Show
      RedoLogCompactionAllPersistentTest RedoLogCompactionAllTransientTest RedoLogCompactionBasicTest RedoLogCompactionManyTransientPacketsTest RedoLogCompactionMirrorAndLocalViewTest RedoLogCompactionTakeMultipleTest RedoLogCompactionSkipAllPersistentRangesOptimizationTest RedoLogTxnCompactionBasicTest
    • Sprint:
      12.3-M20
    • Edition:
      Open Source

      Description

      When a mirror disconnects but the backup is still connected, the primary keeps the packets until the mirror reconnects so it can pick up where it left off.

      If some of the entries are transient, they'll be sent to the mirror as discarded packets, but until then their kept in the redolog as full packets, which affects resource consumption and redolog threshold.

      The solution is to detect that and compact the redolog - if the mirror is disconnected but the backup is active, the redolog should detect transient packets (and ranges of those packets), and replace them with discarded packets to reduce resource consumption while the mirror is disconnected.

        Attachments

          Issue links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: