Stop mapping WiredTiger verbose=tiered on the server

XMLWordPrintableJSON

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

      Problem

      WiredTiger WT-18492 removes the verbose=tiered choice and WT_VERB_TIERED. The server still maps that category in wiredtiger_util.cpp: a case WT_VERB_TIERED: and "tiered" in generateWTVerboseConfiguration(), which is always passed to wiredtiger_open / reconfigure.

      Vendoring WT-18492 without this change will not compile (missing WT_VERB_TIERED). Leaving only the string would fail engine open (tiered is no longer a permitted verbose choice).

      This must land on master before that WiredTiger change is vendored. It is forward-compatible while WT still accepts tiered.

      Change* Delete case WT_VERB_TIERED: in getWTLogComponent().

      • Delete {{ {kWiredTigerTiered, "tiered"}

        }} from the verbose component map.

      • Remove kWiredTigerTiered / wtTiered from log_component.h if nothing else references it.

      Do not vendor WiredTiger in this ticket.

      Test

      bazel run //src/mongo/db/storage/wiredtiger:wiredtiger_util_test (or the existing target for that file). Confirm generated verbose config no longer contains tiered:.

            Assignee:
            Luke Pearson
            Reporter:
            Luke Pearson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: