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

Shard crash when updating record

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Critical - P2 Critical - P2
    • None
    • Affects Version/s: 2.6.0
    • Component/s: Querying, Sharding
    • None
    • ALL
    • Hide

      The update query:

      db.Listings.update({_id: ObjectId('540dade8e4b0e398ab8e7957')}, { $pop: { listingImages: -1 } }, { multi: true })

      on console it triggers this error:

      write results unavailable from 10.0.0.99:27017 :: caused by :: Location17255 error receiving write command response, possible socket exception - see logs

      and on shard log:

      2014-09-08T13:45:23.033+0000 [conn5] SEVERE: Invalid access at 
address: 0x20076a4b82
2014-09-08T13:45:23.040+0000 [conn5] SEVERE: Got signal: 11 (Segmentation fault).
Backtrace:0x11bd301 0x11bc6de 0x11bc7cf 0x7f469ea7dcb0 0x796892 0x796fbf 0x79773d 0x78f974 0x78fd42 0xc220ee 0xc430b9 0xc3ce61 0xc48ca6 0x9ffb41 0xa002d0 0xa01b5f 0xa030bd 0xa06dbe 0xa1cfda 0xa1e04e 
 /usr/bin/mongod(_ZN5mongo15printStackTraceERSo+0x21) [0x11bd301]
 /usr/bin/mongod() [0x11bc6de]
 /usr/bin/mongod() [0x11bc7cf]
 /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0) [0x7f469ea7dcb0]
 /usr/bin/mongod(_ZNK5mongo11mutablebson8Document4Impl12writeElementINS_16BSONArrayBuilderEEEvjPT_PKNS_10StringDataE+0x52) [0x796892]
 /usr/bin/mongod(_ZNK5mongo11mutablebson8Document4Impl13writeChildrenINS_16BSONArrayBuilderEEEvjPT_+0x4f) [0x796fbf]
 /usr/bin/mongod(_ZNK5mongo11mutablebson8Document4Impl12writeElementINS_14BSONObjBuilderEEEvjPT_PKNS_10StringDataE+0x22d) [0x79773d]
 /usr/bin/mongod(_ZN5mongo11mutablebson8Document11makeElementENS0_12ConstElementEPKNS_10StringDataE+0x64) [0x78f974]
 /usr/bin/mongod(_ZN5mongo11mutablebson8Document27makeElementWithNewFieldNameERKNS_10StringDataENS0_12ConstElementE+0x22) [0x78fd42]
 /usr/bin/mongod(_ZNK5mongo11ModifierPop3logEPNS_10LogBuilderE+0x10e) [0xc220ee]
 /usr/bin/mongod(_ZN5mongo12UpdateDriver6updateERKNS_10StringDataEPNS_11mutablebson8DocumentEPNS_7BSONObjEPNS_11FieldRefSetE+0x319) [0xc430b9]
 /usr/bin/mongod(_ZN5mongo6updateERKNS_13UpdateRequestEPNS_7OpDebugEPNS_12UpdateDriverEPNS_14CanonicalQueryE+0xc71) [0xc3ce61]
 /usr/bin/mongod(_ZN5mongo14UpdateExecutor7executeEv+0x66) [0xc48ca6]
 /usr/bin/mongod() [0x9ffb41]
 /usr/bin/mongod(_ZN5mongo18WriteBatchExecutor10execUpdateERKNS_12BatchItemRefEPNS_7BSONObjEPPNS_16WriteErrorDetailE+0x80) [0xa002d0]
 /usr/bin/mongod(_ZN5mongo18WriteBatchExecutor11bulkExecuteERKNS_21BatchedCommandRequestEPSt6vectorIPNS_19BatchedUpsertDetailESaIS6_EEPS4_IPNS_16WriteErrorDetailESaISB_EE+0x1df) [0xa01b5f]
 /usr/bin/mongod(_ZN5mongo18WriteBatchExecutor12executeBatchERKNS_21BatchedCommandRequestEPNS_22BatchedCommandResponseE+0x8cd) [0xa030bd]
 /usr/bin/mongod(_ZN5mongo8WriteCmd3runERKSsRNS_7BSONObjEiRSsRNS_14BSONObjBuilderEb+0x3de) [0xa06dbe]
 /usr/bin/mongod(_ZN5mongo12_execCommandEPNS_7CommandERKSsRNS_7BSONObjEiRSsRNS_14BSONObjBuilderEb+0x3a) [0xa1cfda]
 /usr/bin/mongod(_ZN5mongo7Command11execCommandEPS0_RNS_6ClientEiPKcRNS_7BSONObjERNS_14BSONObjBuilderEb+0xd5e) [0xa1e04e]
      Show
      The update query: db.Listings.update({_id: ObjectId( '540dade8e4b0e398ab8e7957' )}, { $pop: { listingImages: -1 } }, { multi: true }) on console it triggers this error: write results unavailable from 10.0.0.99:27017 :: caused by :: Location17255 error receiving write command response, possible socket exception - see logs and on shard log: 2014-09-08T13:45:23.033+0000 [conn5] SEVERE: Invalid access at address: 0x20076a4b82 2014-09-08T13:45:23.040+0000 [conn5] SEVERE: Got signal: 11 (Segmentation fault). Backtrace:0x11bd301 0x11bc6de 0x11bc7cf 0x7f469ea7dcb0 0x796892 0x796fbf 0x79773d 0x78f974 0x78fd42 0xc220ee 0xc430b9 0xc3ce61 0xc48ca6 0x9ffb41 0xa002d0 0xa01b5f 0xa030bd 0xa06dbe 0xa1cfda 0xa1e04e /usr/bin/mongod(_ZN5mongo15printStackTraceERSo+0x21) [0x11bd301] /usr/bin/mongod() [0x11bc6de] /usr/bin/mongod() [0x11bc7cf] /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0) [0x7f469ea7dcb0] /usr/bin/mongod(_ZNK5mongo11mutablebson8Document4Impl12writeElementINS_16BSONArrayBuilderEEEvjPT_PKNS_10StringDataE+0x52) [0x796892] /usr/bin/mongod(_ZNK5mongo11mutablebson8Document4Impl13writeChildrenINS_16BSONArrayBuilderEEEvjPT_+0x4f) [0x796fbf] /usr/bin/mongod(_ZNK5mongo11mutablebson8Document4Impl12writeElementINS_14BSONObjBuilderEEEvjPT_PKNS_10StringDataE+0x22d) [0x79773d] /usr/bin/mongod(_ZN5mongo11mutablebson8Document11makeElementENS0_12ConstElementEPKNS_10StringDataE+0x64) [0x78f974] /usr/bin/mongod(_ZN5mongo11mutablebson8Document27makeElementWithNewFieldNameERKNS_10StringDataENS0_12ConstElementE+0x22) [0x78fd42] /usr/bin/mongod(_ZNK5mongo11ModifierPop3logEPNS_10LogBuilderE+0x10e) [0xc220ee] /usr/bin/mongod(_ZN5mongo12UpdateDriver6updateERKNS_10StringDataEPNS_11mutablebson8DocumentEPNS_7BSONObjEPNS_11FieldRefSetE+0x319) [0xc430b9] /usr/bin/mongod(_ZN5mongo6updateERKNS_13UpdateRequestEPNS_7OpDebugEPNS_12UpdateDriverEPNS_14CanonicalQueryE+0xc71) [0xc3ce61] /usr/bin/mongod(_ZN5mongo14UpdateExecutor7executeEv+0x66) [0xc48ca6] /usr/bin/mongod() [0x9ffb41] /usr/bin/mongod(_ZN5mongo18WriteBatchExecutor10execUpdateERKNS_12BatchItemRefEPNS_7BSONObjEPPNS_16WriteErrorDetailE+0x80) [0xa002d0] /usr/bin/mongod(_ZN5mongo18WriteBatchExecutor11bulkExecuteERKNS_21BatchedCommandRequestEPSt6vectorIPNS_19BatchedUpsertDetailESaIS6_EEPS4_IPNS_16WriteErrorDetailESaISB_EE+0x1df) [0xa01b5f] /usr/bin/mongod(_ZN5mongo18WriteBatchExecutor12executeBatchERKNS_21BatchedCommandRequestEPNS_22BatchedCommandResponseE+0x8cd) [0xa030bd] /usr/bin/mongod(_ZN5mongo8WriteCmd3runERKSsRNS_7BSONObjEiRSsRNS_14BSONObjBuilderEb+0x3de) [0xa06dbe] /usr/bin/mongod(_ZN5mongo12_execCommandEPNS_7CommandERKSsRNS_7BSONObjEiRSsRNS_14BSONObjBuilderEb+0x3a) [0xa1cfda] /usr/bin/mongod(_ZN5mongo7Command11execCommandEPS0_RNS_6ClientEiPKcRNS_7BSONObjERNS_14BSONObjBuilderEb+0xd5e) [0xa1e04e]

      Hi there,

      we have a cluster setup with 2 shards, 3 configs, and couple of routers, until now everything works great, we are in production for couple months now.

      Trying to do a routine update on couple records, and somehow this specific update query we are doing makes one of the shards crash. Not sure if this is a bug, or me doing something wrong.

            Assignee:
            randolph@mongodb.com Randolph Tan
            Reporter:
            eriol Eriol Gjergji
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: