[SERVER-13465] Shard with replica set name of "admin" triggers dassert Created: 02/Apr/14  Updated: 28/Jan/19  Resolved: 28/Jan/19

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.6.0-rc2
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Shaun Verch Assignee: Janna Golden
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Sprint: Sharding 2019-02-11
Participants:

 Description   

2014-04-02T16:16:21.154-0400 [Balancer] distributed lock 'balancer/sv.local:27017:1396469721:16807' acquired, ts : 533c7014c82dea452b90e6d8
2014-04-02T16:16:21.154-0400 [Balancer] *** start balancing round
2014-04-02T16:16:21.154-0400 [Balancer] waitForDelete: 0
2014-04-02T16:16:21.154-0400 [Balancer] secondaryThrottle: 1
2014-04-02T16:16:21.156-0400 [Balancer] no collections to balance
2014-04-02T16:16:21.156-0400 [Balancer] no need to move any chunk
2014-04-02T16:16:21.156-0400 [Balancer] *** end of balancing round
2014-04-02T16:16:21.157-0400 [conn5] Request::process end ns: admin.$cmd msg id: 2 op: 2004 attempt: 0 11ms
2014-04-02T16:16:21.158-0400 [conn5] Request::process begin ns: test.system.indexes msg id: 3 op: 2002 attempt: 0
2014-04-02T16:16:21.159-0400 [conn5] src/mongo/s/dbclient_shard_resolver.cpp 43 chooseWriteHost - shardName: admin
2014-04-02T16:16:21.159-0400 [conn5] Fatal Assertion 16199
2014-04-02T16:16:21.170-0400 [conn5] 0x100993d85 0x1008fbba4 0x1008d156b 0x10000c180 0x10070c17b 0x1007ee267 0x10064ab68 0x10064c7b1 0x10065e0d9 0x10077e91d 0x100690285 0x1007a5a2f 0x10077d5b9 0x10000565f 0x10091087e 0x10090ea01 0x10090ea66 0x10090eaa1 0x100a09879 0x7fff8e38a772
 0   mongos                              0x0000000100993d85 _ZN5mongo15printStackTraceERSo + 37
 1   mongos                              0x00000001008fbba4 _ZN5mongo10logContextEPKc + 228
 2   mongos                              0x00000001008d156b _ZN5mongo13fassertFailedEi + 139
 3   mongos                              0x000000010000c180 _ZN5mongo7fassertEib + 48
 4   mongos                              0x000000010070c17b _ZN5mongo20DBClientMultiCommand7sendAllEv + 197
 5   mongos                              0x00000001007ee267 _ZN5mongo14BatchWriteExec12executeBatchERKNS_21BatchedCommandRequestEPNS_22BatchedCommandResponseE + 2811
 6   mongos                              0x000000010064ab68 _ZN5mongo13ClusterWriter10shardWriteERKNS_21BatchedCommandRequestEPNS_22BatchedCommandResponseE + 948
 7   mongos                              0x000000010064c7b1 _ZN5mongo13ClusterWriter5writeERKNS_21BatchedCommandRequestEPNS_22BatchedCommandResponseE + 3811
 8   mongos                              0x000000010065e0d9 _ZN5mongo15ClusterWriteCmd3runERKSsRNS_7BSONObjEiRSsRNS_14BSONObjBuilderEb + 633
 9   mongos                              0x000000010077e91d _ZN5mongo7Command22execCommandClientBasicEPS0_RNS_11ClientBasicEiPKcRNS_7BSONObjERNS_14BSONObjBuilderEb + 1339
 10  mongos                              0x0000000100690285 _ZN5mongo7Command20runAgainstRegisteredEPKcRNS_7BSONObjERNS_14BSONObjBuilderEi + 941
 11  mongos                              0x00000001007a5a2f _ZN5mongo8Strategy7writeOpEiRNS_7RequestE + 781
 12  mongos                              0x000000010077d5b9 _ZN5mongo7Request7processEi + 1817
 13  mongos                              0x000000010000565f _ZN5mongo21ShardedMessageHandler7processERNS_7MessageEPNS_21AbstractMessagingPortEPNS_9LastErrorE + 243
 14  mongos                              0x000000010091087e _ZN5mongo17PortMessageServer17handleIncomingMsgEPv + 2302
 15  mongos                              0x000000010090ea01 _ZN5boost3_bi5list1INS0_5valueIPN5mongo17PortMessageServer22HandleIncomingMsgParamEEEEclIPvPFSA_SA_ENS0_5list0EEET_NS0_4typeISE_EERT0_RT1_l + 79
 16  mongos                              0x000000010090ea66 _ZN5boost3_bi6bind_tIPvPFS2_S2_ENS0_5list1INS0_5valueIPN5mongo17PortMessageServer22HandleIncomingMsgParamEEEEEEclEv + 82
 17  mongos                              0x000000010090eaa1 _ZN5boost6detail11thread_dataINS_3_bi6bind_tIPvPFS4_S4_ENS2_5list1INS2_5valueIPN5mongo17PortMessageServer22HandleIncomingMsgParamEEEEEEEE3runEv + 37
 18  mongos                              0x0000000100a09879 thread_proxy + 169
 19  libsystem_c.dylib                   0x00007fff8e38a772 _pthread_start + 327
2014-04-02T16:16:21.170-0400 [conn5]
 
***aborting after fassert() failure

I believe the issue is here: https://github.com/mongodb/mongo/blob/master/src/mongo/s/dbclient_shard_resolver.cpp#L44 If we have a shard called "admin" or "config", this function will return a connection to the config servers.



 Comments   
Comment by Janna Golden [ 28/Jan/19 ]

I haven't been able to reproduce this in 3.6, 4.0 or master. Closed as Gone Away.

Comment by Kaloian Manassiev [ 24/Jan/19 ]

janna.golden, since you are looking at that code path now, I am assigning SERVER-13464 and SERVER-13465 to you to check whether they are still a problem starting in 3.6, where we threw out the DBClientMultiCommand.

Please close them if they are no longer reproducible.

Generated at Thu Feb 08 03:31:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.