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
An unhealthy destination that was excluded from the available destination list can eventually recover and start receiving traffic again. By default, it will get the same load as it was before the failure. It is a fast way to recover the full system capacity that is justified in case the root cause of the failure is fixed for good. However, if the issue is not fully solved and the destination is still unstable, an instant increase of the load can overwhelm it and bring down again.
To avoid such outcome, it's proposed to add a gradual destination warm-up strategy. This can be achieved by assigning to all destinations the new weight value in range (0, 1] controlling the probability of a destination being chosen by the load balancer. By default all destination gets 1, but if one failed and then recovered, its weight gets reset to 0 and then gradually increased back to 1.
The text was updated successfully, but these errors were encountered:
An unhealthy destination that was excluded from the available destination list can eventually recover and start receiving traffic again. By default, it will get the same load as it was before the failure. It is a fast way to recover the full system capacity that is justified in case the root cause of the failure is fixed for good. However, if the issue is not fully solved and the destination is still unstable, an instant increase of the load can overwhelm it and bring down again.
To avoid such outcome, it's proposed to add a gradual destination warm-up strategy. This can be achieved by assigning to all destinations the new weight value in range (0, 1] controlling the probability of a destination being chosen by the load balancer. By default all destination gets 1, but if one failed and then recovered, its weight gets reset to 0 and then gradually increased back to 1.
The text was updated successfully, but these errors were encountered: