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

wiredtiger_open() returns WT_RUN_RECOVERY when recovery is enabled

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Fixed
    • Affects Version/s: WT2.6.0
    • Fix Version/s: WT2.6.1
    • Labels:
      None
    • # Replies:
      11
    • Last comment by Customer:
      true

      Description

      Hi!

      Occasionally after non-clean shutdown (crash) wiredtiger_open() returns us WT_RUN_RECOVERY even though we don't specify log=(recover=error) config.
      If I understand documentation correctly when no value for log=(recover) is given WiredTiger should perform recovery automatically if it needs to.

      On next open it recovers without any problems.

      Unfortunately I have no DB/test now, but maybe it's something known (already fixed)?

      Thanks!

        Issue Links

          Activity

          Hide
          keith.bostic Keith Bostic added a comment -

          Dmitri Shubin, just FYI, the fixes for the wt utility incorrectly creating the WiredTiger.basecfg file have been merged into the WiredTiger develop branch.

          Show
          keith.bostic Keith Bostic added a comment - Dmitri Shubin , just FYI, the fixes for the wt utility incorrectly creating the WiredTiger.basecfg file have been merged into the WiredTiger develop branch.
          Hide
          sue.loverso Sue LoVerso added a comment -

          FTR, Keith and I talked and we think that, similar to other use-this-time-only config settings, the recover=error should not be stored in the base config file.

          Show
          sue.loverso Sue LoVerso added a comment - FTR, Keith and I talked and we think that, similar to other use-this-time-only config settings, the recover=error should not be stored in the base config file.
          Hide
          Dmitri Shubin Dmitri Shubin added a comment -

          Thank you!

          Show
          Dmitri Shubin Dmitri Shubin added a comment - Thank you!
          Hide
          xgen-internal-githook Githook User added a comment -

          Author:

          {u'username': u'keithbostic', u'name': u'Keith Bostic', u'email': u'keith@wiredtiger.com'}

          Message: Strip out the "log=(recover=)" configuration from the base configuration
          file, we don't want wt to create a database and have that be part of the
          base configuration. Reference WT-1943.
          Branch: develop
          https://github.com/wiredtiger/wiredtiger/commit/eb1ab6f69ac464c1456d1cde5555e1d83f5e377d

          Show
          xgen-internal-githook Githook User added a comment - Author: {u'username': u'keithbostic', u'name': u'Keith Bostic', u'email': u'keith@wiredtiger.com'} Message: Strip out the "log=(recover=)" configuration from the base configuration file, we don't want wt to create a database and have that be part of the base configuration. Reference WT-1943 . Branch: develop https://github.com/wiredtiger/wiredtiger/commit/eb1ab6f69ac464c1456d1cde5555e1d83f5e377d
          Hide
          xgen-internal-githook Githook User added a comment -

          Author:

          {u'username': u'keithbostic', u'name': u'Keith Bostic', u'email': u'keith@wiredtiger.com'}

          Message: Don't write a base configuration file unless creating the database,
          WT-1943.

          Move the base configuration file configuration merge code into the base
          configuration create function; it would be nice to leave the merge code
          with the other encryption configuration processing, but this keeps all
          the base configuration file creation checking in one place.
          Branch: develop
          https://github.com/wiredtiger/wiredtiger/commit/a52e29a0bb1ef6d4cb2aa5a773e4db93f68867bd

          Show
          xgen-internal-githook Githook User added a comment - Author: {u'username': u'keithbostic', u'name': u'Keith Bostic', u'email': u'keith@wiredtiger.com'} Message: Don't write a base configuration file unless creating the database, WT-1943 . Move the base configuration file configuration merge code into the base configuration create function; it would be nice to leave the merge code with the other encryption configuration processing, but this keeps all the base configuration file creation checking in one place. Branch: develop https://github.com/wiredtiger/wiredtiger/commit/a52e29a0bb1ef6d4cb2aa5a773e4db93f68867bd

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Days since reply:
                1 year, 46 weeks, 1 day ago
                Date of 1st Reply: