-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
oc scale against a dc is fragile in the presence of races #4327
Comments
whatever we do here, we should come up with a pattern that makes sense for the |
Let's open an upstream issue - "Client commands tend to race against On Tue, Aug 25, 2015 at 12:30 AM, Jordan Liggitt notifications@github.com
Clayton Coleman | Lead Engineer, OpenShift |
New/related upstream issue to lay the foundation for safe concurrent scaling/deployment: kubernetes/kubernetes#14062 |
probably addressed by dc/scale changes |
Fixed by #5875 |
Such confidence. On Wed, Dec 9, 2015 at 9:46 AM, Dan Mace notifications@github.com wrote:
|
|
It doesn't even touch the DC. |
But the scaling endpoint |
Attempting to scale a DC while the controller is creating new RCs returns confusing and vague error messages. If the conditional create of an RC fails (because it's being updated by the DC), we should reload the RC and check that it still current (not failed or completed) and try once more to save. Even a few retries (well factored) would make this a safer experience.
The text was updated successfully, but these errors were encountered: