-
Notifications
You must be signed in to change notification settings - Fork 187
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
"CLUSTER_DISK_IOPS_INVALID" related error/unexpected update-in-place #439
Comments
Also happening to me as of today. Wasn't happening last week. |
@bnelson729 thank you for the issue. So the good thing is the new default IOPS is now 3000k. The error is also expressing that. However you did not set the default iops but you did set If anyone else has the same issue and is setting provider_disk_iops, change it to: I'll update the documentation to reflect this new IOPS default. Also, @robbiet480 this just launched today so that's why you are seeing this error. Is your configuration specific on iops? |
Will bump |
It took 4 minutes, 51 seconds to "modify" but did eventually complete. Still seeing 330 IOPS in the Atlas Console though. |
Oopsies, nevermind, was looking at the wrong cluster! Seeing 3000 IOPS now. Just to confirm, there's no pricing change right? |
@robbiet480 There is no change in price with this change in default IOPS. |
Also, @robbiet480 are we good to close this? |
For me yes, but I didn't open the issue so you may want to wait to see what @bnelson729 says? |
Same happening for us today. Changing the IOPS to 3000 "fixes" the problem and changes the MongoDB cluster's IOPS from 100 to the new minimum 3000. Did Altas change from gp2 to gp3 for AWS? |
@nikhil-mongo let's keep this open till we ensure we have got the word out and ensure the original issue is corrected. |
I changed our M10 and M20 clusters from 100 to 3000 without a problem. But its not working for our M30 cluster. If I want to change from 150 IOPS to 3000 and Terraform seems to be doing it and finishes the apply. But it's still 150 in the GUI and if I ran Terraform again the wants to do 150 -> 3000 again.
On the next apply he tries to do it again with the same result. Still 150
|
Thanks to everyone for the input and alerting. So as you noticed the default IOPS changed for new clusters (and some existing clusters). This was released by Atlas yesterday and obviously this impacted Terraform. It is truly a good thing overall in that the default IOPS is now higher with no increase in cost. The tough thing was the impact this has to IaC use cases and for that we apologize. The team has applied a change to the API so that no matter what IOPS is requested, if it is less than or equal to the default or not possible for that tier as STANDARD, the API will ignore it. This should prevent the errors you encountered. I have updated the documentation to remove IOPS from the examples as well since it's only needed when one desires (and is able by cluster tier) to use PROVISIONED storage with a higher IOPS than the default. Furthermore, for existing clusters the default roll out is happening over time. @pitthecat I believe this may be what is happening in your situation, until your existing clusters are upgraded they will not have higher IOPS. The API now accepts the change even if it's not possible to prevent the aforementioned errors. Thanks! fyi @shum @nikhil-mongo |
I believe we have corrected all the issues and new docs are out. Thank you all for the help!! |
Terraform CLI and Terraform MongoDB Atlas Provider Version
Terraform Configuration File
Steps to Reproduce
On 4/21/2021 at 12:00pm EDT, I ran
terraform apply
without any issue.On 4/21/2021 at 3:05pm EDT, I ran
terraform apply
without any changes.Expected Behavior
Re-running
terraform apply
without any changes shouldn't cause terraform to apply anything.Actual Behavior
When terraform refreshed the state from Atlas by calling the API, the API must have returned that
provider_volume_type
was null. It then created a terraform plan and tried to apply a patch settingprovider_volume_type
from null toSTANDARD
. I believe something changed on your API that is making terraform think it needs to apply this patch.The full plan looks like this (I replaced anything identifable with asterisks):
Debug Output
N/A
Crash Output
Additional Context
No
References
N/A
The text was updated successfully, but these errors were encountered: