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

Segfault while dropping an index that failed to build

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.6.9
    • Component/s: Index Maintenance
    • None
    • Environment:
      3 node replica set
    • Query
    • Linux

      We have a user hitting a situation where they

      1. started a background build on index A, a sparse index
      2. attempted to build index B concurrently on the same collection, which failed with

       Btree::insert: key too large to index 

      3. this failure closed the collection's cursors, which in turn also caused the build of index A to fail
      4. the background index A build fails, but the index is still listed in db.col.getIndexes()
      5. the user attempts to drop to index A with the intention of rebuilding it, but on removing the index, they get

      2015-08-12T18:01:55.540-0700 [conn503836] SEVERE: Invalid access at address: 0
      2015-08-12T18:01:55.546-0700 [conn503836] SEVERE: Got signal: 11 (Segmentation fault).
      Backtrace:0x1219651 0x1218a2e 0x1218b1f 0x7f2172d84cb0 0x8dcd27 0xb999d5 0x948df7 0x94bf59 0xa31b8a 0xa33d21 0xa35468 0xd74992 0xbb2bd2 0xbb41f0 0x7728f8 0x11cedeb 0x7f2172d7ce9a 0x7f21720902ed
       /home/madmin/deploy/lib/mongodb/bin/mongod(_ZN5mongo15printStackTraceERSo+0x21) [0x1219651]
       /home/madmin/deploy/lib/mongodb/bin/mongod() [0x1218a2e]
       /home/madmin/deploy/lib/mongodb/bin/mongod() [0x1218b1f]
       /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0) [0x7f2172d84cb0]
       /home/madmin/deploy/lib/mongodb/bin/mongod(_ZN5mongo12IndexCatalog23killMatchingIndexBuildsERKNS0_17IndexKillCriteriaE+0x217) [0x8dcd27]
       /home/madmin/deploy/lib/mongodb/bin/mongod(_ZN5mongo12IndexBuilder23killMatchingIndexBuildsEPNS_10CollectionERKNS_12IndexCatalog17IndexKillCriteriaE+0x15) [0xb999d5]
       /home/madmin/deploy/lib/mongodb/bin/mongod(_ZN5mongo14CmdDropIndexes15stopIndexBuildsEPNS_8DatabaseERKNS_7BSONObjE+0x407) [0x948df7]
       /home/madmin/deploy/lib/mongodb/bin/mongod(_ZN5mongo14CmdDropIndexes3runERKSsRNS_7BSONObjEiRSsRNS_14BSONObjBuilderEb+0x179) [0x94bf59]
       /home/madmin/deploy/lib/mongodb/bin/mongod(_ZN5mongo12_execCommandEPNS_7CommandERKSsRNS_7BSONObjEiRSsRNS_14BSONObjBuilderEb+0x3a) [0xa31b8a]
       /home/madmin/deploy/lib/mongodb/bin/mongod(_ZN5mongo7Command11execCommandEPS0_RNS_6ClientEiPKcRNS_7BSONObjERNS_14BSONObjBuilderEb+0x1691) [0xa33d21]
       /home/madmin/deploy/lib/mongodb/bin/mongod(_ZN5mongo12_runCommandsEPKcRNS_7BSONObjERNS_11_BufBuilderINS_16TrivialAllocatorEEERNS_14BSONObjBuilderEbi+0x6f8) [0xa35468]
       /home/madmin/deploy/lib/mongodb/bin/mongod(_ZN5mongo11newRunQueryERNS_7MessageERNS_12QueryMessageERNS_5CurOpES1_+0x23d2) [0xd74992]
       /home/madmin/deploy/lib/mongodb/bin/mongod() [0xbb2bd2]
       /home/madmin/deploy/lib/mongodb/bin/mongod(_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_11HostAndPortE+0x5a0) [0xbb41f0]
       /home/madmin/deploy/lib/mongodb/bin/mongod(_ZN5mongo16MyMessageHandler7processERNS_7MessageEPNS_21AbstractMessagingPortEPNS_9LastErrorE+0x98) [0x7728f8]
       /home/madmin/deploy/lib/mongodb/bin/mongod(_ZN5mongo17PortMessageServer17handleIncomingMsgEPv+0x50b) [0x11cedeb]
       /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a) [0x7f2172d7ce9a]
       /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f21720902ed]
      

            Assignee:
            backlog-server-query Backlog - Query Team (Inactive)
            Reporter:
            kyle.erf Kyle Erf
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: