A pacemaker MariaDB resource does not restart properly sometimes on RHEL 7
Issue
- A node in an HA cluster is running a resource
ocf:heartbeat:mysqlto manage amariadbresource . Sometimes after rebooting a cluster node and after pacemaker starts, aocf:heartbeat:mysqlresource does not start properly because of an error that requires the tables to be manually checked for the database. - Is it possible to automate the
check tablecommand when manual intervention is required for the aMariaDBresource?
Environment
- Red Hat Enterprise Linux Server 7 (with the High Availability Add Ons)
mariadb- A
pacemakerresourceocf:heartbeat:mysql(The resourceocf:heartbeat:mysqlmanagesmariadbormysqldatabases.)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.