[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" ] } |
| 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, |
| Comment by Andrew zhou [ 12/Jan/18 ] |
|
hi Kaloian Manassiev |
| Comment by Kaloian Manassiev [ 11/Jan/18 ] |
|
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, |
| Comment by Andrew zhou [ 11/Jan/18 ] |
|
This Problem find in MongoDB shell version: 3.0.12 |