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

Fix tiered file and object metadata configuration

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • WT10.0.1, 4.4.7, 5.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None

      There are some anomalies in the metadata created when using tiered storage. This ticket should investigate and fix those anomalies.
      1. When creating a non-tiered table in a tiered database, the metadata ends up with tiered_storage=(name=none) instead of the default tiered_storage configuration settings.
      2. The metadata table does not end up configured for tiered. It is created before tiered storage is set up.
      3. The history store table does not end up configured for tiered. It is created after tiered storage is set up so this is interesting.
      4. Other create configuration settings seem to get lost when creating a tiered table. One example is to set internal_page_max=16K and the tiered table will end up with the default of 4K.

            sue.loverso@mongodb.com Susan LoVerso
            sue.loverso@mongodb.com Susan LoVerso
            0 Vote for this issue
            1 Start watching this issue