[SERVER-57738] sharding cluster, clients cannot connect to mongos successfully Created: 16/Jun/21 Updated: 22/Jun/21 Resolved: 22/Jun/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.4.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Xana Wang | Assignee: | Eric Sedor |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
I found my clients or mongo shell cannot connect to mongos occasionally. Mongo shell showed that it was connecting, but timed out. After I stepDown config server primary, all the clients can immediately connected. Is this a bug which had been fix in 4.4.6 or some of my configurations aren't correct? Log of mongos or config server seems nothing wrong. |
| Comments |
| Comment by Eric Sedor [ 22/Jun/21 ] |
|
Happy to help, xanawang@gmail.com! |
| Comment by Xana Wang [ 21/Jun/21 ] |
|
It seems my problem was caused by |
| Comment by Eric Sedor [ 16/Jun/21 ] |
|
What you describe could be caused by If not, then we'll need more information: I've created a secure upload portal for you. Files uploaded to this portal are visible only to MongoDB employees and are routinely deleted after some time. 1) Select a specific mongos to connect to, and obtain the timeout errors and timestamps (with time zone) for failed connection attempts to that mongos
For all four of these nodes spanning a time period that includes the unsuccessful connection, the failover, and the successful connection, would you please archive (tar or zip) and upload to the above link:
|
| Comment by Xana Wang [ 16/Jun/21 ] |
|
in addition, mongos did not exit, it just can't be connected and accepted the connection just after the stepDown of config server. |