ExportXMLWordPrintableJSON

    • Type: New Feature
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Engines - Server Integration
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Each applied LSN must contiguously chain from the previous one regardless of which source served it. Right now the chain gap check (12908000) only ever sees entries from the ReadLog stream

      Make sure entries applied from the ORP read stream pass the same contiguity check, and that the first LS entry after a cutback is checked against the last ORP applied LSN (and the same when we go back to ORP). Any gap here should crash like currently. The ORP start LSN is exclusive so we shouldn't see duplicates so asserting that is safe.

      Any test for this should cover ORP -> LS, LS -> ORP -> LS with gaps

            Assignee:
            Clarisse Cheah
            Reporter:
            Clarisse Cheah
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: