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

Update package deployment process to move Publish-Dispatcher instances in ASG to standby #454

Open
mbloch1986 opened this issue May 6, 2022 · 0 comments

Comments

@mbloch1986
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Deploying an AEM package using the current deployment process may cause a Publisher instance to terminate during the deployment.

This can happen if the Publish-Dispatcher ALB Health Check keeps failing during the deployment, which will mark the Publish-Dispatcher as unhealthy. The ASG goes ahead and terminates the unhealthy Publish-Dispatcher. Due to the current orchestration process, the orchestrator will automatically terminate the paired publisher instance. As a result the infrastructure is unstable and the deployment process will fail. A rebuild of the AEM stack might be required.

To reduce the risk of an unstable AEM stack, we should update the deployment process to move the Publish-Dispatcher EC2 instances into standby, before deploying the packages.

Describe the solution you'd like
Updating the deployment process to move the Publish-Dispatcher into standby, before starting the deployment process. Either one by one or all at once.

Describe alternatives you've considered
Keeping the current process.

@mbloch1986 mbloch1986 changed the title Update package deployment process to move EC2 instances in ASG to standby Update package deployment process to move Publish-Dispatcher instances in ASG to standby May 6, 2022
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