ExportXMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Declined
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Engines - Server Integration
    • SESIKhuuBeanz 2026-10-06, SESIPreview 2026-10-20, SESIroflcopter 2026-11-03
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      As part of the materialization lag improvement work, we need to decouple materialization frontier updates from Mongo-side ReadLog processing.

       

      Currently, if ReadLog ingestion or processing becomes slow, PALI may continue observing a stale materialization frontier even though Log service has already progressed. The long-term solution is a dedicated log service frontier-only metadata stream, but that API is not currently available. 

       

      Implement a temp playground path using existing log service apis so that we can validate the PALI-side frontier decoupling independently of the final LS API.

       

      For the primary , reuse frontier updates already available thru the existing AppendLog response stream. For a secondary, when ReadLog ingestion is slow or unable to provide sufficiently fresh frontier info, use GetCurrentLogInfo as a temp polling mechanism to retrieve the current frontier independently of readLog processing.

            Assignee:
            Nic Hollingum
            Reporter:
            Yanxi Wang (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: