Verify accounts for followers missing stable constituent prior to checkpoint pickup

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Verify
    • None
    • Storage Engines, Storage Engines - Persistence
    • SE Persistence - 2025-09-26
    • 3

      Currently, verify expects the stable constituent of layered tables to always exist. This however does not account for a transient exception: a follower can temporarily operates with only an ingest constituent until it picks up its first checkpoint. The follower cannot create stable tables, so the stable table will only appear after the follower picks up a checkpoint created by the leader (or during step-up).

      When we run layered table verification, iff:

      • It is a follower node AND
      • It has no stable constituent AND
      • It has not picked up its first checkpoint since creation

      Then print a clear message explaining that the stable table verification is being skipped due to this transient state.

      We should not fall into the stable URI is NULL assertion so we don't encountering an ENOENT No such file or directory error when in this transient state.

            Assignee:
            Mariam Mojid
            Reporter:
            Mariam Mojid
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: