You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given the following config, any time the weight of a real server is changed, the routing type is set to the same as the service with the lowest fwmark.
I have tried different combinations of routing types and fwmarks, the consistent thing is that the real servers are always changed with the type of the service with the lowest fwmark value. The only error I have managed to catch that may be relevant is:
Given the following config, any time the weight of a real server is changed, the routing type is set to the same as the service with the lowest fwmark.
After a fresh start of the service it looks correct:
After allowing the test on the second real service to succeed:
I have tried different combinations of routing types and fwmarks, the consistent thing is that the real servers are always changed with the type of the service with the lowest fwmark value. The only error I have managed to catch that may be relevant is:
[2021-01-08 11:26:48.877753] debug : * add_dest: [0.0.0.0:0 proto=6 fwmark=2 :: XXXX:80 proto=6 fwmark=2] [2021-01-08 11:26:48.877907] debug : * ERROR add_dest: [0.0.0.0:0 proto=6 fwmark=2 :: XXXX:80 proto=6 fwmark=2] [File exists]
which only occurs when the lower fwmark service is changed.
The text was updated successfully, but these errors were encountered: