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

wiredtiger cant be --repair after shutdown

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • 3.2.1
    • WiredTiger
    • None
    • ALL

    Description

      Hello,

      we have problem with running one of shards in sharding cluster after unclear shutdown.
      We tried to repair it with --repair but log is the same as for service mongod restart.

      [root@reports-sh01 ~]# sudo -u mongod mongod --repair -f /etc/mongod.conf.repair
      2016-02-21T02:13:07.849+0300 I CONTROL  [initandlisten] MongoDB starting : pid=21928 port=27017 dbpath=/var/lib/mongo 64-bit host=reports-sh01.prls.net
      2016-02-21T02:13:07.849+0300 I CONTROL  [initandlisten] db version v3.2.1
      2016-02-21T02:13:07.849+0300 I CONTROL  [initandlisten] git version: a14d55980c2cdc565d4704a7e3ad37e4e535c1b2
      2016-02-21T02:13:07.849+0300 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.1e-fips 11 Feb 2013
      2016-02-21T02:13:07.849+0300 I CONTROL  [initandlisten] allocator: tcmalloc
      2016-02-21T02:13:07.849+0300 I CONTROL  [initandlisten] modules: none
      2016-02-21T02:13:07.849+0300 I CONTROL  [initandlisten] build environment:
      2016-02-21T02:13:07.849+0300 I CONTROL  [initandlisten]     distmod: rhel62
      2016-02-21T02:13:07.849+0300 I CONTROL  [initandlisten]     distarch: x86_64
      2016-02-21T02:13:07.849+0300 I CONTROL  [initandlisten]     target_arch: x86_64
      2016-02-21T02:13:07.849+0300 I CONTROL  [initandlisten] options: { config: "/etc/mongod.conf.repair", repair: true, storage: { dbPath: "/var/lib/mongo", engine: "wiredTiger", wiredTiger: { collectionConfig: { blockCompressor: "none" }, engineConfig: { directoryForIndexes: true, journalCompressor: "snappy", statisticsLogDelaySecs: 30 }, indexConfig: { prefixCompression: true } } } }
      2016-02-21T02:13:07.870+0300 I STORAGE  [initandlisten] Detected WT journal files.  Running recovery from last checkpoint.
      2016-02-21T02:13:07.870+0300 I STORAGE  [initandlisten] journal to nojournal transition config: create,cache_size=1G,session_max=20000,eviction=(threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=30),
      2016-02-21T02:13:07.879+0300 E STORAGE  [initandlisten] WiredTiger (-31802) [1456009987:879562][21928:0x7fc7ee60cd40], file:WiredTiger.wt, connection: WiredTiger.wt read error: failed to read 4096 bytes at offset 73728: WT_ERROR: non-specific WiredTiger error
      2016-02-21T02:13:07.880+0300 I -        [initandlisten] Assertion: 28718:-31802: WT_ERROR: non-specific WiredTiger error
      2016-02-21T02:13:07.880+0300 I STORAGE  [initandlisten] exception in initAndListen: 28718 -31802: WT_ERROR: non-specific WiredTiger error, terminating
      2016-02-21T02:13:07.880+0300 I CONTROL  [initandlisten] dbexit:  rc: 100
      

      I've added WiredTiger.turtle and WiredTiger.wt it attr.

      Attachments

        1. mongod.conf
          0.6 kB
        2. repair_attempt.tgz
          4 kB
        3. sizeStorer.wt
          36 kB
        4. WiredTiger.turtle
          0.9 kB
        5. WiredTiger.wt
          68 kB

        Activity

          People

            Unassigned Unassigned
            scopenco Andrei Skopenko
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: