With binlogging enabled (all earlier tests were with binlogging disabled) but wsrep-load-data-splitting=ON (the default), it doesn't crash anywhere but I still see
2014-02-19 17:06:22 19006 [Warning] MySQL is closing a connection that has an active InnoDB transaction. 4 row modifications will roll back.
With binlogging enabled (all earlier tests were with binlogging disabled) but wsrep-load- data-splitting= ON (the default), it doesn't crash anywhere but I still see
2014-02-19 17:06:22 19006 [Warning] MySQL is closing a connection that has an active InnoDB transaction. 4 row modifications will roll back.
======= ======= ======= ======= ======= ======= ======= ======= ======= ==
To conclude,
When wsrep-load- data-splitting= ON
a) Binlogging being disabled leads to crash with UNIV_DEBUG builds and lost rows.
b) With binlogging enabled, it doesn't crash but it still loses rows when connection is closed.
When wsrep-load- data-splitting= OFF
there are no issues at all.