We should open the checkpoint of shared metadata in the follower

XMLWordPrintableJSON

    • Storage Engines - Foundations
    • 4,062.143
    • SE Foundations - 2026-03-27, SE Foundations - 2026-04-10
    • 5

      Here's the code we open the shared metadata in __disagg_pick_up_checkpoint. This is called by the follower. Thus, we should open a checkpoint of the shared metadata but from the code we are opening the shared metadata as a live btree.

          cfg[0] = WT_CONFIG_BASE(session, WT_SESSION_open_cursor);
    cfg[1] = NULL;
    WT_ERR(__wt_open_cursor(shared_metadata_session, WT_DISAGG_METADATA_URI, NULL, cfg, &cursor));

      There are other places we open the shared metadata the same way.
      We need to ensure we only open checkpoint of shared tables when we are the follower. Can we add some verification to detect this?

        1. test.js
          4 kB

            Assignee:
            Jie Chen
            Reporter:
            Chenhao Qu
            Alex Blekhman
            Votes:
            0 Vote for this issue
            Watchers:
            18 Start watching this issue

              Created:
              Updated:
              Resolved: