-
Notifications
You must be signed in to change notification settings - Fork 179
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
better rolling of asgs #107
Conversation
@@ -551,7 +554,9 @@ | |||
"UpdatePolicy": { | |||
"AutoScalingRollingUpdate": { | |||
"MaxBatchSize": 1, | |||
"MinInstancesInService": 1 | |||
"MinInstancesInService": 1, | |||
"PauseTime" : "PT15M", |
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.
Does it roll faster than this if it receives the signal?
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.
Yes that's just a timeout for receiving all the signals. We could even bump it to 20 or 30
On Oct 16, 2015, at 8:13 AM, David Dollar notifications@github.com wrote:
In api/dist/kernel.json:
@@ -551,7 +554,9 @@
"UpdatePolicy": {
"AutoScalingRollingUpdate": {
"MaxBatchSize": 1,
"MinInstancesInService": 1
"MinInstancesInService": 1,
Does it roll faster than this if it receives the signal?"PauseTime" : "PT15M",
—
Reply to this email directly or view it on GitHub.
👍 |
wait for resource signals, 15m timeout send signals after cfn-init completes note: does not wait for ecs-agent or convox start to finish.
simple first pass
cfn-init
completesnote: does not wait for ecs-agent or convox start to finish.