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

recovery messages always appear in the log, even after clean shutdown

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Works as Designed
    • Icon: Major - P3 Major - P3
    • None
    • None
    • WiredTiger
    • None
    • Fully Compatible
    • ALL
    • Hide

      1. Run mongod on an empty data directory.
      2. Shut down mongod cleanly.
      3. Restart mongod and note system log messages.

      Show
      1. Run mongod on an empty data directory. 2. Shut down mongod cleanly. 3. Restart mongod and note system log messages.

    Description

      If I shut down a mongod cleanly and restart it, I always see these messages appear in the log:

      2017-10-16T23:20:51.470-0400 I STORAGE  [initandlisten] WiredTiger message [1508210451:470968][12311:0x7fab9e63c480], txn-recover: Main recovery loop: starting at 17/4992
      2017-10-16T23:20:51.520-0400 I STORAGE  [initandlisten] WiredTiger message [1508210451:520816][12311:0x7fab9e63c480], txn-recover: Recovering log 17 through 18
      2017-10-16T23:20:51.521-0400 I STORAGE  [initandlisten] WiredTiger message [1508210451:521173][12311:0x7fab9e63c480], txn-recover: Recovering log 18 through 18
      

      (I noticed them appearing in our jstest output.)
      Is this expected? Something may have changed recently to cause the "17 through 18" message to always appear. The original ticket that turned on verbosity was SERVER-16796, but I don't think the messages appeared back then; something changed more recently.

      Attachments

        Activity

          People

            sue.loverso@mongodb.com Susan LoVerso
            milkie@mongodb.com Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: