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

mongoD 3.2.10 crashes with Invariant failure false src\mongo\db\storage\mmap_v1\btree\btree_logic.cpp 1746

    • Type: Icon: Bug Bug
    • Resolution: Incomplete
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: MMAPv1
    • None
    • ALL

      Environment:

      • Mongo 3.2.10
      • Windows Server 2012
      • Replicaset with 2 mongoD's (mmapv1) + arbiter
      • Cluster with 3 config servers in CSRS + mongoS

      After we upgraded from 3.0.4 to 3.2.10, we're seeing one of the 2 mongoD's constantly crashing. Here's the relevant entries in mongod.log:

      2016-11-01T10:20:26.800-0700 I -        [repl writer worker 13] Invariant failure false src\mongo\db\storage\mmap_v1\btree\btree_logic.cpp 1746^M
      2016-11-01T10:20:26.800-0700 I -        [repl writer worker 13] ^M
      ^M
      ***aborting after invariant() failure^M
      ^M
      ^M
      2016-11-01T10:20:27.098-0700 I CONTROL  [repl writer worker 13] mongod.exe      index_collator_extension+0x1a4663^M
      2016-11-01T10:20:27.098-0700 I CONTROL  [repl writer worker 13] mongod.exe      index_collator_extension+0x1a35a4^M
      2016-11-01T10:20:27.098-0700 I CONTROL  [repl writer worker 13] mongod.exe      index_collator_extension+0x1a2fc6^M
      2016-11-01T10:20:27.098-0700 I CONTROL  [repl writer worker 13] MSVCR120.dll    raise+0x1e9^M
      2016-11-01T10:20:27.098-0700 I CONTROL  [repl writer worker 13] MSVCR120.dll    abort+0x18^M
      2016-11-01T10:20:27.098-0700 I CONTROL  [repl writer worker 13] mongod.exe      index_collator_extension+0x14c713^M
      2016-11-01T10:20:27.099-0700 I CONTROL  [repl writer worker 13] mongod.exe      ???^M
      

            Assignee:
            kelsey.schubert@mongodb.com Kelsey Schubert
            Reporter:
            alessandro.gherardi@yahoo.com Alessandro Gherardi
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: