Handle the case that passes a checkpoint_meta config to primary

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Configuration
    • Storage Engines, Storage Engines - Foundations
    • None
    • None

      In the disagg prototype implementation, we choose to ignore the checkpoint_meta configuration in primary. We don't throw an error is because the old config can remain in the system before the node steps-up as the primary.

      Handle this case properly.

            Assignee:
            [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            Chenhao Qu
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: