-
Notifications
You must be signed in to change notification settings - Fork 33
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
Bug: Take Database Count Into Consideration #286
Comments
In the short term you can set minSize in your scaling configuration to 800 to prevent it from scaling smaller than that, but I understand that this is not a long term solution if the number of databases changes rapidly. |
Thanks, yes we have taken that action |
nielm
added a commit
to nielm/autoscaler
that referenced
this issue
May 10, 2024
Instances configured with <1000 PUs only support 10 DBs per 100 PUs so clamp the minimum size to the relevant number of PUs Fixes cloudspannerecosystem#286
nielm
added a commit
to nielm/autoscaler
that referenced
this issue
May 10, 2024
Instances configured with <1000 PUs only support 10 DBs per 100 PUs so clamp the minimum size to the relevant number of PUs Fixes cloudspannerecosystem#286
nielm
added a commit
to nielm/autoscaler
that referenced
this issue
May 27, 2024
Instances configured with <1000 PUs only support 10 DBs per 100 PUs so clamp the minimum size to the relevant number of PUs Fixes cloudspannerecosystem#286
nielm
added a commit
that referenced
this issue
May 28, 2024
Instances configured with <1000 PUs only support 10 DBs per 100 PUs so clamp the minimum size to the relevant number of PUs Fixes #286
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello and thank you 🙏
Error we are experiencing:
From https://cloud.google.com/spanner/quotas#database-limits
Possible solutions:
The text was updated successfully, but these errors were encountered: