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
2 ways to choose a best peer, but I'm having some problems as my peer connection was full due to slow response time, so I have some idea, is to choose the best peer-based on two factors:
response time of peer, if the peer does have the fastest response time, then select the best peer.
The number of error messages returned (400,404,500). If any peer returns an error message at least choose the best peer.
Plase. help me.
If possible, please guide me how to write ideas on.
The text was updated successfully, but these errors were encountered:
Write your logic there, though you'll probably need to adapt ngx_http_upstream_get_fair_peer() and ngx_http_upstream_free_fair_peer() to collect relevant statistics. You'll probably want an exponential weighted moving average to store the response time with low overhead and something similar that gives less weight to old data for the error counter so that a backend having issues in the past isn't penalised too much.
2 ways to choose a best peer, but I'm having some problems as my peer connection was full due to slow response time, so I have some idea, is to choose the best peer-based on two factors:
Plase. help me.
If possible, please guide me how to write ideas on.
The text was updated successfully, but these errors were encountered: