Reduce the number of configurations needed to turn on disagg in WT

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Engines - Foundations
    • SE Foundations - Q4+ Backlog
    • None

      Recently I have been writing a performance test for DSC mode WT. I found the UX of enabling disagg to be confusing. Firstly I was of the opinion that it would be sufficient to simply enable either "leader" or "follower" via the disaggregrated config. This isn't enough, however, as it seems you also need to enable precise_checkpoint=true . Then you need to choose a "page_log" which I am unclear about but seems to have no default value, options seem to include "palm" and "palite" and possibly "pali"? This is likely muddied as a result of __conn_add_page_log.

      Is it possible to improve on this experience, and reduce the number of configurations required? We could possibly drop the precise_checkpoint configuration, though that may exist as a result of plans for precise checkpoint to become ASC too. In any case a single configuration option being enabled, may be sufficient for MongoDB? Defaulting to PALI and precise checkpoint could achieve that.

            Assignee:
            [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            Luke Pearson
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: