-
Notifications
You must be signed in to change notification settings - Fork 1
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
Set app_replicas to 2 for production #1848
Conversation
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.
Looks good, could we also add a description to the commit explaining why we're making this change?
afbf672
to
a1f1f04
Compare
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.
Code looks great, I would like to see a description in the commit message of why we're making this change.
I also wonder if there's anything we need to be careful of when deploying this as obviously we can't test it in any non-production environments? Should this change also be applied to pre-production?
During the last AKS cluster upgrade, the app had a small outage. We suspect it's because it's deployed with only 1 replica, hence we increasing the number of repicas to 2.
a1f1f04
to
7044ae9
Compare
On the infrastructure side, it's a very common configuration so there is no risk here. The only issue would be if the app is stateful and keeps something in the container as requests will now be spread across 2 instances. But I think we would have seen issue before, as containers are restarted from time to time which would remove the state. |
No description provided.