Assigned
Status Update
No update yet.
Comments
el...@doit.com
I have filed your feature request to our product team. However, there is no guarantee that this feature will be implemented, and the ETA cannot be provided. Rest assured that your feedback is always taken into account, as it allows us to improve the platform.
Any future updates to this feature will be posted here.
Any future updates to this feature will be posted here.
Description
- Getting "InnoDB: Database was not shut down normally!" in their logs but doesn't expose to them that out-of-memory killer would shutdown MySQL.
What you would like to accomplish:
- Out-of-memory message in Stackdriver logging to reveal the out-of-memory killer would shutdown MySQL because it was the biggest memory user in the system
Other information (workarounds you have tried, documentation consulted, etc):
- upgrade instance machine type, but having an explicit reason would be beneficial.
How this might work:
- Explicitly expose OOM events in Stackdriver Logging to the customer when MySQL DB restarts
- Reveal when customer's instance will run out of CPU / RAM / disk space in the Cloud Console
If applicable, reasons why alternative solutions are not sufficient: N/A
Other information (workarounds you have tried, documentation consulted, etc):
----
I have forwarded this request to the Cloud SQL engineering team for further evaluation. But I cannot guarantee if or when it will be implemented. However, the public can indicate interest in this feature by "starring" this thread (next to the Issue Tracker number at the top left-hand corner of the thread) to increase general awareness and participation level. Stay tuned for future updates here.