Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-39978

Take a global lock to quiesce the database before configuring `wiredTigerEngineRuntimeConfig`

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Gone away
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Storage
    • Labels:
      None
    • Sprint:
      Storage Engines 2019-04-08
    • Case:

      Description

      When changing the WiredTiger storage engine config string, the database must be quiescent, otherwise it will fail with "system must be quiescent for upgrade or downgrade".

      Currently neither the setParameter command nor the code associated with the wiredTigerEngineRuntimeConfig parameter takes the steps such as acquiring a global X lock to quiesce the database. So it's possible that the WT reconfiguration would fail. It would be nice if we can try to take a global lock to quiesce the database before configuring `wiredTigerEngineRuntimeConfig`.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              sue.loverso Susan LoVerso
              Reporter:
              linda.qin Linda Qin
              Participants:
              Votes:
              1 Vote for this issue
              Watchers:
              12 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: