[SERVER-39978] Take a global lock to quiesce the database before configuring `wiredTigerEngineRuntimeConfig` Created: 06/Mar/19  Updated: 27/Oct/23  Resolved: 08/Apr/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Linda Qin Assignee: Susan LoVerso
Resolution: Gone away Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to WT-4693 WT_CONNECTION::reconfigure should not... Closed
Sprint: Storage Engines 2019-04-08
Participants:
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`.



 Comments   
Comment by Susan LoVerso [ 02/Apr/19 ]

I have opened WT-4693 to fix this issue.

Generated at Thu Feb 08 04:53:41 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.