ExportXMLWordPrintableJSON

    • Type: New Feature
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Engines - Server Integration
    • SESIroflcopter 2026-11-03, SESIWhinery 2026-11-17, SESINickBeckenhome 2026-12-01
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Right now we ask ORP for an LSN range in a single request so the request can be large ranges and the stream can stay open for a long time. ORP wants to be able to break up long reads for load shedding purposes

      On our end, we'd need to split ORP reads into stages reads and have the standby continue from the last oplog entry it received. these planned disruptions from ORP should come with a marker (like complete = False) so we know that it's not a failure and it should not cause a backoff or count as a retry. We should also have guarantee from ORP that we will receive at least one entry for the early end streams. Between stages of a continuous read, the standby should check if the LS can serve us and we can switch back. Metrics should be added, magic restore logic should be untouched

      Splitting this work into a few tickets, this ticket should handle ORP yielding before a read is complete as well as resuming from the last successfully enqueued LSN without taking up retry attempts after we've yielded from ORP. Keep retries bounded when no progress is made

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

              Created:
              Updated: