Skip to content
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

Offline-Snapshot process does not wait until EC2 instance is in standby #47

Open
mbloch1986 opened this issue Nov 30, 2020 · 0 comments

Comments

@mbloch1986
Copy link
Contributor

At the beginning of the oflfine-snapshot process EC2 instances of the Author-Dispatcher & Publish-Dispatcher are getting moved into standby. As configured in the Classic Load Balancer Draining Policy or in the ALB Target Group deregistration_delay configuration, it can take up to 5 minutes until those EC2 instances are in standby.

The offline-snapshot process will fail in the scenario where it takes up to 5 minutes to move the EC2 instances into standby and the offline-snapshot process finishes within 5 minutes. Because the process tries to move the ec2 instances from standby into in service at the end, while those ec2 instances are not in standby yet.

Lambda Error message

ClientError: An error occurred (ValidationError) when calling the ExitStandby operation: The instance i-... is not in Standby.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant