FSM: no such a transition ROLLED_BACK -> ROLLED_BACK

137 views
Skip to first unread message

Andrew Jack

unread,
Jun 8, 2015, 5:34:46 AM6/8/15
to codersh...@googlegroups.com
Hi there,

I'm getting an intermittent issue in my cluster thats crashing nodes.

I had a crash on a node this weekend which had wsrep_debug = 1 so I have slightly more detailed logs of what occured but I'm still not sure what the issue is.

150607 12:06:33 [Note] WSREP: Forcing release of transactional locks for thd 83
150607 12:06:33 [Note] WSREP: Forcing release of transactional locks for thd 83
150607 12:06:33 [Warning] WSREP: SQL statement was ineffective, THD: 83, buf: 187
QUERY: commit
 => Skipping replication
150607 12:06:33 [Note] WSREP: commit failed for reason: 3
150607 12:06:33 [Note] WSREP: conflict state: 0
150607 12:06:33 [Note] WSREP: cluster conflict due to certification failure for threads:
150607 12:06:33 [Note] WSREP: Victim thread:
   THD: 83, mode: local, state: executing, conflict: cert failure, seqno: -1
   SQL: commit
150607 12:06:33 [ERROR] WSREP: FSM: no such a transition ROLLED_BACK -> ROLLED_BACK
150607 12:06:33 [ERROR] mysqld got signal 6 ;

So far everything I've read says that this issue is caused by an incorrectly set bin_log but I'm using ROW on all 5 nodes

MariaDB [(none)]> show variables like 'binlog_format';
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| binlog_format | ROW   |
+---------------+-------+
1 row in set (0.00 sec)

I've attached a copy of the node that crashed no the weekends my.cnf

All nodes have almost identical my.cnf files (barring the obvious name changes)
my.cnf

Philip Stoev

unread,
Jun 8, 2015, 7:27:39 AM6/8/15
to Andrew Jack, codersh...@googlegroups.com
Hello,

In this case I would say your best bet would be to upgrade to the latest
version, as indicated in the MDEV-7217 ticket.

As a very last resort, you can double-check your SQL queries and attempt to
remove any instances of the following, in the hope that it is what triggers
the problem:
* the binlog_format being manipulated dynamically or per-session, overriding
your global binlog_format setting.
* LOAD DATA INFILE, CREATE ... SELECT
* InnoDB tables without a primary key
* MyISAM or temporary tables

Thank you.

Philip Stoev
--
You received this message because you are subscribed to the Google Groups
"codership" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to codership-tea...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages