max_connect_errors on database server #IP# is #VALUE# which is less than 999999 for clusterid #CID#. Please refer to ScaleArc configuration guide.
|Release||Document Status||DB Platform||Categories|
|3.5 or higher||WARNING||MySQL||Cluster Settings|
After ScaleArc is upgraded to 3.5 or later, ScaleArc starts highlighting an error message similar to one shown below.
max_connect_errors on database server 192.168.0.1 is 10 which is less than 999999 for clusterid 1. Please refer to ScaleArc configuration guide.
The default settings for MySQL database, max_connections = 151 and max_connect_errors = 10, would not be sufficient for ScaleArc to operate since MySQL database servers could block all ScaleArc accesses due to too many connection errors.
B.5.2.6 Host 'host_name' is blocked
In prior to ScaleArc 3.5, ScaleArc allows users to create a cluster with a database server whose max_connections and max_connect_errors variables are set less than 999999. After ScaleArc 3.5 onwards, this became a requirement.
Please consider to increase such variables by issuing a command shown below within running MySQL database server in prior to creating a new cluster. (Set the connections to fit your environement and load. In this example we use 999999. The minimum required to configure a cluster in ScaleArc is 300.
Plus, please consider to specify such variables in your MySQL configration in order to make these settings parmanent.
In case your cluster has been pre-configured prior to the upgrade, our health check still succeeds. You may choose to keep using such database server, but this is not recommended.
If you are experiencing issues with ScaleArc or with any of it's features, please contact ScaleArc Support. We are available 24x7 by phone at 855 800 7225 or +1 408 412 7315. For general support inquiries, you can also e-mail us at firstname.lastname@example.org.
2901 Tasman Drive Santa Clara, CA 95054 | Email: email@example.com