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

Investigate why the sweep server cannot be reconfigured (6.0 and lower)

    • Type: Icon: Task Task
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: DHandles
    • None
    • Storage Engines
    • 2
    • StorEng - Defined Pipeline

      It looks like the sweep server cannot be reconfigured on 6.0 and lower:

      1. Launch a 4.4.29 replica set with the following config file (I was also able to reproduce with MongoDB 6.0.20) :
      
      2. Wait for few minutes and change the sweep server parameter :
      db.adminCommand({setParameter: 1, wiredTigerEngineRuntimeConfig: "file_manager=(close_handle_minimum=100,close_idle_time=30,close_scan_interval=1800)" })
      
      3. Parameters are enforced : wait for at least 30 minutes for the sweep server to execute.
      
      4. Change again the parameter :
       db.adminCommand({setParameter: 1, wiredTigerEngineRuntimeConfig: "file_manager=(close_handle_minimum=150,close_idle_time=600,close_scan_interval=10)" })
      
      5. Wait for at least 30 minutes again until the next sweep server pass which is necessary for the parameters to apply.
      
      6. The sweep server is now executing every 30 seconds :
      
      Outcome : it seems that the sweep server ignored the command executed during step 4 instructing him to execute every 10 seconds. It came back to the parameter specified in the config file.
      
      Expected result : the sweep server should execute every 30 seconds.
      

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            etienne.petrel@mongodb.com Etienne Petrel
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: