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

Consolidate capacity and block manager bytes written

    • Type: Icon: Technical Debt Technical Debt
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • WT3.2.0, 4.0.7, 4.1.9
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Storage Engines 2019-02-11
    • v4.0

      With WT-4447, there is now a redundancy in information and action. With the io_capacity configuration setting, there is a background thread that walks the file handles, in the os_common code. The file handle now contains a written field that is incremented when wt_write is called and cleared when the handle is sync'ed by the capacity background thread.

      Similarly, there is support for os_cache_dirty_max and os_cache_max settings on a table. When data is written to a table, the block manager code increments block->os_cache_dirty and will sync the file handle associated with that table.

      That is now the same/very similar information being kept in two locations. The block manager code should be modified to use or call into the file handle code to use its mechanism.

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