-
Notifications
You must be signed in to change notification settings - Fork 228
Move retry logic for scale from zero into rio #952
Conversation
stacks/rio-autoscaler-stack.yaml
Outdated
@@ -7,7 +7,7 @@ services: | |||
- '* autoscale.rio.cattle.io/servicescalerecommendations' | |||
- '* rio.cattle.io/services' | |||
- '* rio.cattle.io/services/status' | |||
image: rancher/rio-autoscaler:v0.1.5 | |||
image: daxl/rio-autoscaler:dev3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Depends on rancher/rio-autoscaler#11
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💯
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, curious as to how 2 seconds was decided on ?
@@ -2,6 +2,9 @@ package vsfactory | |||
|
|||
import ( | |||
"net" | |||
"time" | |||
|
|||
"github.com/solo-io/gloo/projects/gloo/pkg/api/v1/options/retries" | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: space
// Retry configuration for the envoy gateway (Gloo) https://www.envoyproxy.io/learn/automatic-retries | ||
// for services scaled to zero | ||
var overallTimeout = time.Second * 30 | ||
var perTryTimeout = time.Second * 2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was what I saw as a decent timeout for each request. Ultimately I think this may need to be configurable based upon the service being scaled
This moves the retry logic for the scale from zero functionality into the Rio controller where it can be performed by the Envoy proxy (Gloo).
This moves the retry logic for the scale from zero functionality into
the Rio controller where it can be performed by the Envoy proxy (Gloo).
Addresses #607