FAQ

[mongodb-user] mongos crash when auto-sharding -- version 2.0.2

Chancey
Apr 19, 2012 at 9:45 am
Thu Apr 19 17:38:03 [conn13596] Socket say send() errno:32 Broken pipe
202.102.98.25:10000

Thu Apr 19 17:38:03 [conn13596] DBException in process: socket exception

Thu Apr 19 17:38:03 [conn13409] Socket say send() errno:32 Broken pipe
202.102.98.25:10000

Thu Apr 19 17:38:03 [conn13409] DBException in process: socket exception

Thu Apr 19 17:38:03 [conn13634] Socket say send() errno:32 Broken pipe
202.102.98.25:10000

Thu Apr 19 17:38:03 [conn13634] DBException in process: socket exception

Thu Apr 19 17:38:03 [conn13373] Socket recv() errno:104 Connection reset by
peer 202.102.98.25:10000

Thu Apr 19 17:38:03 [conn13373] SocketException: remote: 202.102.98.25:10000
error: 9001 socket exception [1] server [202.102.98.25:10000]

Thu Apr 19 17:38:03 [conn13373] DBClientCursor::init lazy say() failed

Thu Apr 19 17:38:03 [conn13373] DBClientCursor::init message from say() was
empty

Thu Apr 19 17:38:03 [conn13373] warning: invalid result from
shard0001/w-mdb03:10000,w-mdb02:10000,w-mdb01.:10000

Thu Apr 19 17:38:03 [conn13373] DBException in process: could not initialize
cursor across all shards because : error querying server:
shard0001/w-mdb03.:10000,w-mdb02.:10000,w-mdb01.:10000

Thu Apr 19 17:38:03 [conn13373] Socket say send() errno:32 Broken pipe
202.102.98.25:10000

Thu Apr 19 17:38:03 [conn13373] DBException in process: socket exception

Thu Apr 19 17:38:03 [conn12712] Socket recv() errno:104 Connection reset by
peer 202.102.98.25:10000

Thu Apr 19 17:38:03 [conn12712] SocketException: remote: 202.102.98.25:10000
error: 9001 socket exception [1] server [202.102.98.25:10000]

Thu Apr 19 17:38:03 [conn12712] DBClientCursor::init lazy say() failed

Thu Apr 19 17:38:03 [conn12712] DBClientCursor::init message from say() was
empty

Thu Apr 19 17:38:03 [conn12712] warning: invalid result from
shard0001/w-mdb03.:10000,w-mdb02.:10000,w-mdb01.:10000

Thu Apr 19 17:38:03 [conn12712] DBException in process: could not initialize
cursor across all shards because : error querying server:
shard0001/w-mdb03.:10000,w-mdb02.:10000,w-mdb01.:10000

Thu Apr 19 17:38:03 [conn13605] ns: yunpan.datumExist could not initialize
cursor across all shards because : stale config detected for ns:
yunpan.datumExist ClusteredCursor::_checkCursor @
shard0002/w-mdb04.:10001,w-mdb06.:10001,w-mdb05.:10001 attempt: 0

Thu Apr 19 17:38:03 [conn13605] Socket recv() errno:104 Connection reset by
peer 202.102.98.25:10000

Thu Apr 19 17:38:03 [conn13605] SocketException: remote: 202.102.98.25:10000
error: 9001 socket exception [1] server [202.102.98.25:10000]

Thu Apr 19 17:38:03 [conn13605] DBClientCursor::init call() failed

Thu Apr 19 17:38:03 [conn13373] got not master for: w-mdb02.:10000



Received signal 11

Backtrace: 0x54de95 0x34b7a302d0 0x7e9e77 0x7f346e 0x7f3d2d 0x5c1e06
0x5bffe7 0x7680be 0x77286d 0x776a55 0x7b487d 0x7c6cf1 0x5e6a07 0x34b82064a7
0x34b7ad3c2d

/usr/local/mongodb/bin/mongos(_ZN5mongo17printStackAndExitEi+0x75)[0x54de95]

/lib64/libc.so.6[0x34b7a302d0]

/usr/local/mongodb/bin/mongos(_ZN5mongo17WriteBackListener4initERNS_12DBClie
ntBaseE+0x17)[0x7e9e77]

/usr/local/mongodb/bin/mongos[0x7f346e]

/usr/local/mongodb/bin/mongos[0x7f3d2d]

/usr/local/mongodb/bin/mongos(_ZN5boost6detail8function17function_invoker4IP
FbRN5mongo12DBClientBaseERKSsbiEbS5_S7_biE6invokeERNS1_15function_bufferES5_
S7_bi+0x16)[0x5c1e06]

/usr/local/mongodb/bin/mongos(_ZN5mongo15ShardConnection11_finishInitEv+0x13
7)[0x5bffe7]

/usr/local/mongodb/bin/mongos(_ZN5mongo8Strategy7doWriteEiRNS_7RequestERKNS_
5ShardEb+0xde)[0x7680be]

/usr/local/mongodb/bin/mongos(_ZN5mongo13ShardStrategy7_updateERNS_7RequestE
RNS_9DbMessageEN5boost10shared_ptrIKNS_12ChunkManagerEEE+0xf7d)[0x77286d]

/usr/local/mongodb/bin/mongos(_ZN5mongo13ShardStrategy7writeOpEiRNS_7Request
E+0x125)[0x776a55]

/usr/local/mongodb/bin/mongos(_ZN5mongo7Request7processEi+0xdd)[0x7b487d]

/usr/local/mongodb/bin/mongos(_ZN5mongo21ShardedMessageHandler7processERNS_7
MessageEPNS_21AbstractMessagingPortEPNS_9LastErrorE+0x71)[0x7c6cf1]

/usr/local/mongodb/bin/mongos(_ZN5mongo3pms9threadRunEPNS_13MessagingPortE+0
x287)[0x5e6a07]

/lib64/libpthread.so.0[0x34b82064a7]

/lib64/libc.so.6(clone+0x6d)[0x34b7ad3c2d]

===

CursorCache at shutdown - sharded: 2 passthrough: 0

Received signal 11

Backtrace: 0x54de95 0x34b7a302d0 0x7efb1c 0x7f1ba2 0x7eac56 0x7b54cf
0x7b7003 0x779ab6 0x793175 0x76cf2b 0x7b4927 0x7c6cf1 0x5e6a07 0x34b82064a7
0x34b7ad3c2d

/usr/local/mongodb/bin/mongos(_ZN5mongo17printStackAndExitEi+0x75)[0x54de95]

/lib64/libc.so.6[0x34b7a302d0]

/usr/local/mongodb/bin/mongos(_ZNSt8_Rb_treeIN5mongo17WriteBackListener15Con
nectionIdentESt4pairIKS2_NS1_8WBStatusEESt10_Select1stIS6_ESt4lessIS2_ESaIS6
_EE13insert_uniqueESt17_Rb_tree_iteratorIS6_ERKS6_+0xdc)[0x7efb1c]

/usr/local/mongodb/bin/mongos(_ZNSt3mapIN5mongo17WriteBackListener15Connecti
onIdentENS1_8WBStatusESt4lessIS2_ESaISt4pairIKS2_S3_EEEixERS7_+0x222)[0x7f1b
a2]

/usr/local/mongodb/bin/mongos(_ZN5mongo17WriteBackListener7waitForERKNS0_15C
onnectionIdentERKNS_3OIDE+0x86)[0x7eac56]

/usr/local/mongodb/bin/mongos(_ZN5mongo10ClientInfo17_handleWriteBacksERSt6v
ectorINS0_6WBInfoESaIS2_EEb+0x9f)[0x7b54cf]

/usr/local/mongodb/bin/mongos(_ZN5mongo10ClientInfo12getLastErrorERKNS_7BSON
ObjERNS_14BSONObjBuilderEb+0x11d3)[0x7b7003]

/usr/local/mongodb/bin/mongos(_ZN5mongo11dbgrid_cmds23CmdShardingGetLastErro
r3runERKSsRNS_7BSONObjEiRSsRNS_14BSONObjBuilderEb+0x46)[0x779ab6]

/usr/local/mongodb/bin/mongos(_ZN5mongo7Command20runAgainstRegisteredEPKcRNS
_7BSONObjERNS_14BSONObjBuilderEi+0x8b5)[0x793175]

/usr/local/mongodb/bin/mongos(_ZN5mongo14SingleStrategy7queryOpERNS_7Request
E+0x5cb)[0x76cf2b]

/usr/local/mongodb/bin/mongos(_ZN5mongo7Request7processEi+0x187)[0x7b4927]

/usr/local/mongodb/bin/mongos(_ZN5mongo21ShardedMessageHandler7processERNS_7
MessageEPNS_21AbstractMessagingPortEPNS_9LastErrorE+0x71)[0x7c6cf1]

/usr/local/mongodb/bin/mongos(_ZN5mongo3pms9threadRunEPNS_13MessagingPortE+0
x287)[0x5e6a07]

/lib64/libpthread.so.0[0x34b82064a7]

/lib64/libc.so.6(clone+0x6d)[0x34b7ad3c2d]

===





--
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To post to this group, send email to mongodb-user@googlegroups.com.
To unsubscribe from this group, send email to mongodb-user+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/mongodb-user?hl=en.
reply

Search Discussions

2 responses

  • Gregor at Apr 19, 2012 at 10:07 am
    Did the problem re-occur when you restarted mongos?
    Can you try flushRouterConfig?
    http://www.mongodb.org/display/DOCS/flushRouterConfig+command

    --
    You received this message because you are subscribed to the Google Groups "mongodb-user" group.
    To view this discussion on the web visit https://groups.google.com/d/msg/mongodb-user/-/EDsP_a1U7voJ.
    To post to this group, send email to mongodb-user@googlegroups.com.
    To unsubscribe from this group, send email to mongodb-user+unsubscribe@googlegroups.com.
    For more options, visit this group at http://groups.google.com/group/mongodb-user?hl=en.
  • Chancey at Apr 19, 2012 at 11:26 am
    the threads number is too large before the server crash.

    Mongod threads number: 13000+

    Mongos threads number: 13000+







    发件人: mongodb-user@googlegroups.com
    代表 gregor
    发送时间: 2012年4月19日 18:08
    收件人: mongodb-user@googlegroups.com
    主题: [mongodb-user] Re: mongos crash when auto-sharding -- version 2.0.2



    Did the problem re-occur when you restarted mongos?

    Can you try flushRouterConfig?

    http://www.mongodb.org/display/DOCS/flushRouterConfig+command

    --
    You received this message because you are subscribed to the Google Groups
    "mongodb-user" group.
    To view this discussion on the web visit
    https://groups.google.com/d/msg/mongodb-user/-/EDsP_a1U7voJ.
    To post to this group, send email to mongodb-user@googlegroups.com.
    To unsubscribe from this group, send email to
    mongodb-user+unsubscribe@googlegroups.com.
    For more options, visit this group at
    http://groups.google.com/group/mongodb-user?hl=en.

    --
    You received this message because you are subscribed to the Google Groups "mongodb-user" group.
    To post to this group, send email to mongodb-user@googlegroups.com.
    To unsubscribe from this group, send email to mongodb-user+unsubscribe@googlegroups.com.
    For more options, visit this group at http://groups.google.com/group/mongodb-user?hl=en.

Related Discussions

Discussion Navigation
viewthread | post

2 users in discussion

Chancey: 2 posts Gregor: 1 post