Supply the step-down schema epoch with the step-down timestamp

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Storage Engines - Foundations
    • Fully Compatible
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Background

      WiredTiger's WT_CONNECTION::set_timestamp now accepts step_down_disaggregated_schema_epoch alongside step_down_timestamp (WT-18276), declaring the planned step-down boundary in schema-epoch space as well as timestamp space. With the epoch supplied, WiredTiger rejects publishing a schema operation at or below the boundary and asserts at step-down that the stable schema epoch landed on it exactly. Without it, the epoch-side enforcement is skipped.

      Task

      When the server prepares a planned step-down and sets step_down_timestamp, also pass step_down_disaggregated_schema_epoch in the same set_timestamp call, set to the schema epoch the final checkpoint will cover. The parameter is currently optional in WiredTiger; WT-18314 makes it required once the server supplies it.

            Assignee:
            Jie Chen
            Reporter:
            Jie Chen
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: