-
-
Notifications
You must be signed in to change notification settings - Fork 577
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
Changing replica_count causes all instances to be recreated #151
Comments
Looks like problem is with engine_mode setting which for some reason is set to
According to documentation this value defaults to Looks like instance count have nothing to do with this and trying to run code with that setting even without any changes tries to replace entire cluster.
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
For some reason when you change replica_count and then hit apply all instances are being replaced.
I was trying to see if Aurora will actually add and remove instances when you change amount of available instances but all instances are being replaced even tho you either added or removed 1 instance.
Each time I update replica_count from 1 to 2 or from 2 to 3 or from 3 to 2 all instances are being removed.
After investigating logs further noticed that entire cluster is removed and only thing that changed between both runs is above mentioned value.
Terraform apply truncated output below:
The text was updated successfully, but these errors were encountered: