Ingest table is wrongly set with the WT_BTREE_DISAGGREGATED flag

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • WT12.0.0, 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: Btree
    • None
    • Storage Engines, Storage Engines - Transactions
    • SE Transactions - 2025-12-05
    • 3

      The ingest table is not backed by the SLS so it should never be set with the WT_BTREE_DISAGGREGATED flag. However, when MongoDB creates the layered cursor, it uses the "block_manager=disagg" config. This config passes to the ingest table creation as well and causing it to be set with the WT_BTREE_DISAGGREGATED flag.

         if (strstr(btree->dhandle->name, ".wt_stable") != NULL || WT_CONFIG_LIT_MATCH("disagg", cval)) {
              F_SET(btree, WT_BTREE_DISAGGREGATED);
      
              WT_RET(__btree_setup_page_log(session, btree));
      
              /* A page log service and a storage source cannot both be enabled. */
              WT_ASSERT(session, btree->page_log == NULL || btree->bstorage == NULL);
          }
      

            Assignee:
            Chenhao Qu
            Reporter:
            Chenhao Qu
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: