We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8### Verify steps
目前的实现会在连接错误达到 max-failed-times 后直接进行健康检查 而没有将问题节点标记为不可用 如果问题节点一开始的延迟很低 会导致在健康检查结束之前新的连接依旧会被分配到问题节点 尤其是在节点比较多的时候 这个问题尤为明显 因为节点多全部健康检查花的时间也长 故障后要等很久才能恢复网络
mihomo/adapter/outboundgroup/groupbase.go
Lines 263 to 264 in 802267f
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
8### Verify steps
Description
目前的实现会在连接错误达到 max-failed-times 后直接进行健康检查
而没有将问题节点标记为不可用
如果问题节点一开始的延迟很低
会导致在健康检查结束之前新的连接依旧会被分配到问题节点
尤其是在节点比较多的时候
这个问题尤为明显
因为节点多全部健康检查花的时间也长
故障后要等很久才能恢复网络
mihomo/adapter/outboundgroup/groupbase.go
Lines 263 to 264 in 802267f
Possible Solution
No response
The text was updated successfully, but these errors were encountered: