Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-6513

Update history store configuration to make overflow keys unlikely

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • WT10.0.0, 4.9.0, 4.4.5
    • Affects Version/s: None
    • Component/s: None
    • None
    • 5
    • Storage - Ra 2021-01-25, Storage - Ra 2021-02-08, Storage - Ra 2021-02-22

      Our current History Store create configuration string is:

      "key_format="IuQQ",value_format="QQQu",block_compressor="WT_HS_COMPRESSOR                                     ",leaf_value_max=64MB,prefix_compression=false"
      

      We should update the configuration to make it very unlikely that we'll ever use overflow keys in the history store. Probably by setting leaf_key_max and internal_key_max to the same value as leaf_value_max.

      The default value is 1/10th of a page split size. The default page size is 4KB meaning that the overflow size is about 400 bytes. MongoDB could definitely be triggering that with indexes at the moment.

            Assignee:
            sulabh.mahajan@mongodb.com Sulabh Mahajan
            Reporter:
            alexander.gorrod@mongodb.com Alexander Gorrod
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: