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

Dropping Index in WT Corrupted Database

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Cannot Reproduce
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: WiredTiger
    • Labels:
      None
    • Operating System:
      ALL

      Description

      Running WiredTiger with a large "2d" index on a co-ordinate pair on field p
      Created a 2nd index on

      { p: "2d", d : 1}

      as foreground.
      Database is under lead quering and updating.
      All good

      Dropped the original index - database quit immediately.
      Will not restart - log says

      2016-04-07T16:22:48.349+0000 I CONTROL  [initandlisten] options: { config: "/data/MDBWorldOSM/automation-mongod.conf", net: { bindIp: "0.0.0.0", port: 27017 }, processManagement: { fork: true }, storage: { dbPath: "/data/MDBWorldOSM", engine: "wiredTiger", journal: { enabled: false }, wiredTiger: { collectionConfig: { blockCompressor: "zlib" } } }, systemLog: { destination: "file", path: "/data/mongod.log" } }
      2016-04-07T16:22:48.370+0000 W -        [initandlisten] Detected unclean shutdown - /data/MDBWorldOSM/mongod.lock is not empty.
      2016-04-07T16:22:48.370+0000 W STORAGE  [initandlisten] Recovering data from the last clean checkpoint.
      2016-04-07T16:22:48.370+0000 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=37G,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=0),,log=(enabled=false),
      2016-04-07T16:22:48.408+0000 I -        [initandlisten] Fatal assertion 28579 NoSuchKey: Unable to find metadata for table:index-0-3681633574245705750
      2016-04-07T16:22:48.408+0000 I -        [initandlisten]
      

      Database is WT runnign with nojournal - however as I understand it this can at worst lead to 60s of data loss/rollback.

      Database available for inspection in-situ on AWS.

        Attachments

          Activity

            People

            Assignee:
            backlog-server-execution Backlog - Storage Execution Team
            Reporter:
            john.page John Page
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: