Types of Cluster Notifications

MySQL is an open source, object-relational database built with speed and reliability in mind. Its large and active developer community has created many third-party applications, tools, and libraries that expand MySQL’s functionality.


We monitor your database clusters for issues like low disk space and automatic failovers. If we detect an issue, we email you and any team members attached to the account using the account owner’s email address.

This page lists the database cluster issues we send email alerts for. You cannot disable or customize these automatic emails. To receive alerts about issues not covered here (like CPU usage), you can set up cluster monitoring policies based on specified parameters that you choose.

Failover Notifications

When we detect a performance issue in your cluster, such as problems with the underlying Droplet that the cluster is running on, we start a primary node replacement. You don’t need to take any action, but if you have not set up your cluster for high availability, you may experience downtime.

Resource Usage Notifications

We send low resource notifications when your cluster is low on memory or disk space.

  • Low Disk Space: We send this notification when your cluster’s disk space usage reaches greater than 90% of available space for one minute or more within the last five minutes. You can free up disk space by removing unnecessary data, such as errant logs, or by increasing the size of your cluster.

  • Out of Memory: We send this notification when one or more nodes is low on memory and the Out of Memory Killer has stopped two processes in the past six hours.

MySQL Replication Issue

We send notifications when we detect that your MySQL cluster contains at least one table, with 5000 or more rows, doesn’t have any primary keys defined for it for at least one hour. You can fix this by creating a primary key for the table(s) specified in the alert.