-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
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
[BUG] The GlobalTrafficPolicy doesn't failover when weights declared #134
Comments
@wenxian This could be an istio issue, but I remember this was tested at least in istio version |
we are using istio 1.6
I am calling from the us-east-1, actually, i found as long as the local (us-east-1) >= 50, the call always in local (us-east-1) which means 1. the weight doesn't got applied. (10 of 10 in east) 2. it won't fail over to remote (west). |
@wenxian I see the destination rule has been generated with the correct weights as per the spec apparently the distribute sets weights. Outlier detection might not be used here. Probably looking at the envoy clusters night help, can you share the output for the following command: |
us-east-1
I have a set up us-east-1 (admiral server and admiral remote) us-west-2 (admiral remote), actually i see the 50/50 distribute works in west but not in the east. The east cluster goes to west (the LB), but looks like the west LB still returns the east response. So finally it looks like always in the east us-west-2
--- UPDATE --- (US-EAST-1 >= 50, US-WEST-2) -> Request from East will always return East, West is good This means if the cluster (locality) has more weight, it could result in the requests from its own cluster fall in its cluster always. (Because the LB always resolves to its own cluster) |
…ESH-1743-DR-bk MESH-1743 Fix missed vs delete
Describe the bug
If the weight is declared, the 10 times of consecutive5xxErrors won't failover to the other region
Steps To Reproduce
Expected behavior
If a service returns 10 times 500, it won't get kicked off when GTP Weight(90 / 10 ) applied.
Without GTP, the failover will work with 10 consecutive 500 errors
The text was updated successfully, but these errors were encountered: