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
{ // ... "outbounds": [ { "protocol": "freedom", "tag": "direct" }, { // ... "tag": "x1" }, { // ... "tag": "x2" }, { // ... "tag": "y1" }, { // ... "tag": "y2" } ], "routing": { // ... "rules": [ { "type": "field", "balancerTag": "x", "ip": [ "192.168.0.0/24" ] }, { "type": "field", "balancerTag": "y", "ip": [ "192.168.1.0/24" ] } ], "balancers": [ { "tag": "x", "selector": [ "x" ], "strategy": { "type": "leastPing" } }, { "tag": "y", "selector": [ "y" ], "strategy": { "type": "leastPing" } } ] }, "observatory": { "subjectSelector": [ "x", "y" ] // ... } }
期待的行为是192.168.0.0/24走balancer x,192.168.1.0/24走balancer y。 但实际行为是192.168.1.0/24走了direct,可能是balancer y没有匹配到任何outbound的缘故。 为了进一步验证猜想,将balancer y的strategy改为随机:
192.168.0.0/24
balancer x
192.168.1.0/24
balancer y
direct
strategy
{ "tag": "y", "selector": [ "y" ], "strategy": { "type": "random" } }
这时候192.168.1.0/24就走了balancer y,问题就不在了。推测observatory的结果只能被使用一次,或者说只会返回一个最快的结果,如果最快的结果不能被另一个balancer匹配,便没有可用的outbound,从而导致了这个问题。
observatory
另外还有个问题,假设一切工作正常,请问下面的配置会发生什么:
{ // ... "outbounds": [ { "protocol": "freedom", "tag": "direct" }, { // ... "tag": "x1" }, { // ... "tag": "x2" }, { // ... "tag": "xy1" }, { // ... "tag": "xy2" } ], "routing": { // ... "rules": [ { "type": "field", "balancerTag": "x", "ip": [ "192.168.0.0/24" ] }, { "type": "field", "balancerTag": "xy", "ip": [ "192.168.1.0/24" ] } ], "balancers": [ { "tag": "x", "selector": [ "x" ], "strategy": { "type": "leastPing" } }, { "tag": "xy", "selector": [ "xy" ], "strategy": { "type": "leastPing" } } ] }, "observatory": { "subjectSelector": [ "x" // ,"xy" // 应该是多余的,理论上"x"应该已经包括了"xy" ] // ... } }
期待的行为是192.168.0.0/24可走x1, x2, xy1, xy2,192.168.1.0/24走xy1, xy2。
x1, x2, xy1, xy2
xy1, xy2
The text was updated successfully, but these errors were encountered:
可能相关 #872 #1146
Sorry, something went wrong.
能否测一下最新版 如果问题复现 能否测一下 burstObservatory 以及 leastLoad
No branches or pull requests
期待的行为是
192.168.0.0/24
走balancer x
,192.168.1.0/24
走balancer y
。但实际行为是
192.168.1.0/24
走了direct
,可能是balancer y
没有匹配到任何outbound的缘故。为了进一步验证猜想,将
balancer y
的strategy
改为随机:这时候
192.168.1.0/24
就走了balancer y
,问题就不在了。推测observatory
的结果只能被使用一次,或者说只会返回一个最快的结果,如果最快的结果不能被另一个balancer匹配,便没有可用的outbound,从而导致了这个问题。另外还有个问题,假设一切工作正常,请问下面的配置会发生什么:
期待的行为是
192.168.0.0/24
可走x1, x2, xy1, xy2
,192.168.1.0/24
走xy1, xy2
。The text was updated successfully, but these errors were encountered: