Uploaded image for project: 'InsightEdge Platform'
  1. GS-12850

Slow/disconnected Async replication targets that should consume only small amount of packets will cause redolog to grow fast with unrelated operations

    Details

    • Type: Bug
    • Status: Open
    • Priority: Medium
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Platform:
      All
    • SalesForce Case ID:
      10581,11085, 11752,10877
    • Sprint:

      Description

      Reproduction:
      1. in client 1 create Notify Container that listen to type A
      2. in client 2 write type B in a loop
      3. disconnect client 1

      Attached the 2 clients.

      Expected:
      As we don't need to save any notifications for client 1, the redo log should be 0

      Actual:
      The redo log is growing.

      Same differentiation that we should do for types, we need to do for operations as well. Means that when a client listen for write operation. We should not save in the redolog any operations beside write.

        Attachments

          Issue links

            Activity

              People

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

                Dates

                • Created:
                  Updated: