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

WT_CONNECTION::reconfigure should not require quiescence when downgraded

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • WT3.2.0, 4.1.10, 4.0.10, 3.6.14
    • None
    • None
    • 2
    • Storage Engines 2019-04-08
    • v4.0, v3.6

    Description

      If a user is running in a downgraded compatibility mode and calls conn->reconfigure() for any setting, for example, setting cache size, the system will return an error saying the system must be quiescent if there are any outstanding transactions. It should only return an error if the user is actually trying to change the compatibility setting.

      The bug is that reconfigure is passed in the current running configuration string and the new setting added on at the end so the compatibility mode being anything other than the default hits the check in wt_conn_compat_config. That code needs to be restructured to only return an error if the value is changing.

      Attachments

        Issue Links

          Activity

            People

              sue.loverso@mongodb.com Susan LoVerso
              sue.loverso@mongodb.com Susan LoVerso
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: