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

Perform checkpoint cleanup on data store as part of checkpoint

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • WT10.0.0, 4.4.0-rc13, 4.7.0
    • Affects Version/s: 4.4.0-rc11
    • Component/s: None
    • 5
    • Storage - Ra 2020-07-13

      Test inserts 1 M documents in a collection then removes them all. After removing the documents the checkpoint size relative to its size after inserting the documents is not reduced to 0 on the primary, and is only reduced a little on the secondary.

      • After the documents are inserted both nodes have a checkpoint size of 69.5 GB.
      • After the documents are removed the primary has a checkpoint size of 6.0 GB, whereas the secondary still has a checkpoint size of 64.5 GB.
      • Under 4.2 after the documents are removed the checkpoint size is 0 for both nodes, so the non-zero checkpoint size after removal for both 4.4 nodes is problematic, but one more than the other.

      Test is in repro.sh; ftdc attached. Output showing checkpoint sizes of each node (ports 27017 and 27117) after insert, then after remove:

      27017
      69.46484375
      27117
      69.49609375
      
      27017
      5.984375
      27117
      64.5
      

        1. CONFIG.fail
          2 kB
        2. repro.sh
          1 kB
        3. repro2.sh
          1 kB
        4. repro6508.c
          23 kB
        5. tree.jpg
          tree.jpg
          25 kB
        6. x-equal.tar
          1.08 MB

            Assignee:
            haribabu.kommi@mongodb.com Haribabu Kommi
            Reporter:
            bruce.lucas@mongodb.com Bruce Lucas (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            18 Start watching this issue

              Created:
              Updated:
              Resolved: