Fuel for OpenStack

  1. Bug #1350245
  2. Comment #16

Comment 16 for bug 1350245

Revision history for this message
Sergii Golovatiuk (sgolovatiuk) wrote :

The issue is still present. I was able to reproduce it in my environment.

The RCA of issue is

/var/log/mysql/error.log
2014-08-01 11:15:57 3683 [Note] WSREP: /usr/sbin/mysqld: Terminated.
Aborted

/var/log/mysqld.log
<27>Aug 1 11:15:48 node-2 mysql-wss[3767]: ERROR: GTID have wrong format: wsrep_local_state_uuid:18446744073709551615
<27>Aug 1 11:15:48 node-2 mysql-wss[3767]: ERROR: Wrong GTID, not updating gtid attribute
<27>Aug 1 11:16:48 node-2 mysql-wss[4430]: ERROR: MySQL not running: removing old PID file

/var/log/mysql/error.log
2014-08-01 11:17:24 7790 [Note] WSREP: /usr/sbin/mysqld: Terminated.
Aborted

/var/log/mysqld.log
<27>Aug 1 11:17:21 node-2 mysql-wss[7882]: ERROR: GTID have wrong format: wsrep_local_state_uuid:18446744073709551615
<27>Aug 1 11:17:21 node-2 mysql-wss[7882]: ERROR: Wrong GTID, not updating gtid attribute
<27>Aug 1 11:18:22 node-2 mysql-wss[8577]: ERROR: MySQL not running: removing old PID file

/var/log/mysql/error.log
2014-08-01 11:18:57 11783 [Note] WSREP: /usr/sbin/mysqld: Terminated.
Aborted

/var/log/mysqld.log
<27>Aug 1 11:18:54 node-2 mysql-wss[11874]: ERROR: GTID have wrong format: wsrep_local_state_uuid:18446744073709551615
<27>Aug 1 11:18:54 node-2 mysql-wss[11874]: ERROR: Wrong GTID, not updating gtid attribute
<27>Aug 1 11:19:55 node-2 mysql-wss[12593]: ERROR: MySQL not running: removing old PID file

/var/log/mysql/error.log
2014-08-01 11:22:03 20410 [Note] WSREP: /usr/sbin/mysqld: Terminated.
Aborted

/var/log/mysqld.log
<27>Aug 1 11:22:00 node-2 mysql-wss[20516]: ERROR: GTID have wrong format: wsrep_local_state_uuid:18446744073709551615
<27>Aug 1 11:22:00 node-2 mysql-wss[20516]: ERROR: Wrong GTID, not updating gtid attribute
<27>Aug 1 11:23:01 node-2 mysql-wss[22166]: ERROR: MySQL not running: removing old PID file

Comparing MySQL log and Pacemaker log we can see that pacemaker cannot validate GTID as mysqld is in SST/IST state without proper GTID. In this case pacemaker should also verify if MySQL is not in SST/IST state and skip it until transfer is done