Visibility to excessive db splits that hinder new db creation and/or node reduction [327778951]

Assigned

Bug

Status Update

No update yet.

Description

tr...@google.com

created issue #1

Mar 1, 2024 08:47PM

There is a concern about the visibility of database splits limit in their instance, it is unknown when these are going to hit the limit, which would stop from creating new db or scaling down, so it is required to have visibility of database splits to have alerts.

And also it is required to have configuration in OSS autoscaler tool based on database splits to add nodes beforehand and avoid this type of error.

Comments

ch...@davita.com <ch...@davita.com> #2Mar 19, 2024 10:18PM

Forgot to add screenshots.

Message last modified on Mar 19, 2024 10:19PM

ch...@davita.com <ch...@davita.com> #3Apr 1, 2024 04:45PM

Hello,

Thank you for reaching out to us with your request.

We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.

We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, please do not hesitate to create a new issue on the Issue Tracker providing a detailed description of your issue.

Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.

Issue 327778951

Description

Issue summary

Comments

ch...@davita.com <ch...@davita.com> #2Mar 19, 2024 10:18PM

ch...@davita.com <ch...@davita.com> #3Apr 1, 2024 04:45PM

Add comment

Issue metadata