[SERVER-32655] in mongos log will have some couldn't check dbhash on config server DBClientBase::findN: transport error warn,but could read and write data to shard cluster Created: 11/Jan/18  Updated: 27/Oct/23  Resolved: 11/Jan/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.0.12
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Andrew zhou Assignee: Kaloian Manassiev
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Steps To Reproduce:

we only restart the config 10.200.65.131:27019 mongod thread solve this problem。

Participants:

 Description   

内容:2018-01-11 14:10 CST 到 2018-01-11 14:12 CST 期间日志:
couldn't check dbhash on config server 10.200.65.131:27019 :: caused by :: 10276 DBClientBase::findN: transport error: 10.200.65.131:27019 ns: config.$cmd query:

{ dbhash: 1, collections: [ "chunks", "databases", "collections", "shards", "version" ] }

couldn't check dbhash on config server 10.200.65.131:27019 :: caused by :: 10276 DBClientBase::findN: transport error: 10.200.65.131:27019 ns: config.$cmd query:

{ dbhash: 1, collections: [ "chunks", "databases", "collections", "shards", "version" ] }

 Comments   
Comment by Ramon Fernandez Marina [ 13/Jan/18 ]

Please note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. A question like this involving more discussion would be best posted on the mongodb-user group. See also our Technical Support page for additional support resources.

Thanks,
Ramón.

Comment by Andrew zhou [ 12/Jan/18 ]

hi Kaloian Manassiev
I'am want to tell you ,we have too many mongos connects get into connect the config mongod, this will trigger this mongos DBClientBase::findN: transport error ,we find sometime will have 20000-40000 connect from mongos to config ,but mongos only need to have get config metadata,not need too many connnect to config ,because we read and write date is from shard .

Comment by Kaloian Manassiev [ 11/Jan/18 ]

Hi hancang2000@126.com,

The message that you are seeing is just a transient network failure reported by the background thread, which checks the contents of the legacy SCCC config server for consistency. It doesn't imply any configuration data errors and that's why your reads and writes can continue.

Hope this helps.

Best regards,
-Kal.

Comment by Andrew zhou [ 11/Jan/18 ]

This Problem find in MongoDB shell version: 3.0.12

Generated at Thu Feb 08 04:30:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.