Comment 3 for bug 1367562

Hi,

I would like to mention to things:

1- One of the crash are caused because of data inconsistencies:

2014-09-16 12:25:24 14868 [ERROR] Slave SQL: Error 'Table 'xxxx.xxxxbackup_ids_temp' doesn't exist' on query. Default database: 'xxxx'. Query: 'CREATE INDEX xxxxbackidstemp_bacitepar_ix ON xxxxbackup_ids_temp (backupid, itemname, parentitemid)', Error_code: 1146

2014-09-16 12:25:24 14868 [ERROR] Slave SQL: Error 'Table 'xxxx.xxxxbackup_ids_temp' doesn't exist' on query. Default database: 'xxxx'. Query: 'CREATE UNIQUE INDEX xxxxbackidstemp_baciteite_uix ON xxxxbackup_ids_temp (backupid, itemname, itemid)', Error_code: 1146

How are those temporary tables created? Are you creating them in InnoDB?

Those inconsistencies cause crashes after several retries.

2- You use GET_LOCK and RELEASE_LOCK. Those are not supported in Galera, see:

https://blueprints.launchpad.net/codership-mysql/+spec/get-lock-support

3- Can you share: SHOW CREATE TABLE xxxxxxxsessions\G

4- Do you write to that table from different servers? I see rollbacks on queries that affect that table. If your application rely on GET_LOCK to write on xxxxxxxsessions in a consistent way from multiple servers, then you need to review your application logic because as I said, it is not supported in galera and maybe the application is not doing what it is expected to do. This is just an advice, maybe not related with the crash.