Kristian, I didn't know of that function, good to hear that. But I was after some kind of slave_skip_counter-like function to make galera skip an event in case of problems. I'm fine with a cluster member stopping (or going read-only or something like that) because some update couldn't be applied, but if I (for whatever reason) think that's OK and just want it to skip that event, how could I do that? Jan Am 12.02.2013 10:36, schrieb Kristian Nielsen:
Jan Kirchhoff <j.kirchhoff@logical-line.de> writes:
Is there something like slave_skip_counter, aka "I Know what I do, skip that update"? I think I have to take a new snapshot to get the second
Yes, MariaDB has this:
https://kb.askmonty.org/en/selectively-skipping-replication-of-binlog-events...
If you set skip_replication=0 (instead of SQL_LOG_BIN=0) and replicate-events-marked-for-skip=FILTER_ON_MASTER on all servers. Then the changes will be logged to the binlog (for Galera to use), but will not be sent to other slaves using traditional replication.
Disclaimer: I do not have much experience with Galera, much less actually tried using it with @@skip_replication, but it should work, I think.
Note that this is a MariaDB feature (it will not work with Galera based on MySQL or Percona-server).
- Kristian.