[SERVER-21007] When the first config server's network encounter problem(ip can't be ping through), the mongos will be very very slow, seem like hang problem. Created: 19/Oct/15 Updated: 14/Apr/16 Resolved: 22/Oct/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.0.7 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | qianyiyong | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
all |
||
| Issue Links: |
|
||||||||
| Operating System: | Linux | ||||||||
| Participants: | |||||||||
| Description |
|
I tested with 5 servers, 3 config servers, 5 shard servers. I used mongo route server(mongos) to visit the data. I found that when shut down the first config server's network which configured in mongos config file(such as shutdown switch port, ifconfig down server network card, turn off the computer), we can't visit the data well, it's very slow, always it will be cost several minutes.In this situation, the high availability is not good, even has not high availability. |
| Comments |
| Comment by Ramon Fernandez Marina [ 22/Oct/15 ] |
|
qianyiyong@huawei.com, there are some known issues in this area and Regards, |