MySQL Bugs: #100891: pacemaker not starting

Bug #100891	pacemaker not starting
Submitted:	19 Sep 2020 14:14	Modified:	19 Sep 2020 17:56
Reporter:	Ambadas kawle	Email Updates:
Status:	Unsupported	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	mysql-5.1.73-7.el6.x86_64	OS:	CentOS (centos 6.10)
Assigned to:		CPU Architecture:	Any
Tags:	cluster, pacemaker, slave

Description:
Hello All

We have 2 node with mysql cluster and we are not able to start pacemaker on one of the node.
We are getting erro "waiting for quorum... timed-out waiting for cluster"

Following are package detail
pacemaker pacemaker-1.1.15-5.el6.x86_64
    pacemaker-libs-1.1.15-5.el6.x86_64
    pacemaker-cluster-libs-1.1.15-5.el6.x86_64
    pacemaker-cli-1.1.15-5.el6.x86_64
    
Corosync corosync-1.4.7-6.el6.x86_64
    corosynclib-1.4.7-6.el6.x86_64
    
Mysql mysql-5.1.73-7.el6.x86_64
    "mysql-connector-python-2.0.4-1.el6.noarch

How to repeat:
service pacemaker start

Hi Ambadas, 

I'm MySQL Community Manager, no part of support or the bug validation team.

However, I've some comments on your bug report:

1. MySQL 5.1 is very old and not supported anymore ! It was released in November 2008 and support ended in Dec 2013. You should upgrade to 8.0.
2. MySQL Cluster is a product using NDB as storage engine, see https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster.html
3. So pacemaker (with corosync) as nothing to do with MySQL. Of course MySQL (mysqld) could be a resource managed by pacemaker and even if it's possible to hack some replication checks using pacemaker, this will at least require GTIDs that are not present in 5.1

So if you are looking for HA, I would suggest to use MySQL InnoDB ReplicaSet or MySQL InnoDB Cluster.

See:
- https://dev.mysql.com/doc/refman/8.0/en/deploying-innodb-replicasets.html
- https://dev.mysql.com/doc/refman/8.0/en/deploying-production-innodb-cluster.html

You can also find more information on https://lefred.be

And finally to at least answer a bit about your question, the issue is not at all related to MySQL and it seems Corosync/Pacemaker nodes are not able to talk to each others (verify firewall) but also the quorum (even if ignored) needs to be specified.

Regards ;)

Thank you for the bug report. Unsupported and thanks Frederic for the explanation.