mariadb/plugin/semisync
He Zhenxing 64fc766c93 BUG#45674 FLUSH STATUS does not reset semisynchronous counters
Semi-sync status were not reset by FLUSH STATUS, this was because
all semi-sync status variables are defined as SHOW_FUNC and FLUSH
STATUS could only reset SHOW_LONG type variables.

This problem is fixed by change all status variables that should
be reset by FLUSH STATUS from SHOW_FUNC to SHOW_LONG.

After the fix, the following status variables will be reset by
FLUSH STATUS:
  Rpl_semi_sync_master_yes_tx
  Rpl_semi_sync_master_no_tx

Note: normally, FLUSH STATUS itself will be written into binlog
and be replicated, so after FLUSH STATS, one of
  Rpl_semi_sync_master_yes_tx
  Rpl_semi_sync_master_no_tx
can be 1 dependent on the semi-sync status. So it's recommended
to use FLUSH NO_WRITE_TO_BINLOG STATUS to avoid this.
2009-10-12 21:03:04 +08:00
..
configure.in Backporting WL#4398 WL#1720 2009-09-26 12:49:49 +08:00
Makefile.am Backport BUG#45848 Semisynchronous replication internals are visible in SHOW PROCESSLIST and logs 2009-10-12 20:55:01 +08:00
plug.in Backporting WL#4398 WL#1720 2009-09-26 12:49:49 +08:00
semisync.cc Backporting WL#4398 WL#1720 2009-09-26 12:49:49 +08:00
semisync.h Backport BUG#45848 Semisynchronous replication internals are visible in SHOW PROCESSLIST and logs 2009-10-12 20:55:01 +08:00
semisync_master.cc BUG#45674 FLUSH STATUS does not reset semisynchronous counters 2009-10-12 21:03:04 +08:00
semisync_master.h BUG#45674 FLUSH STATUS does not reset semisynchronous counters 2009-10-12 21:03:04 +08:00
semisync_master_plugin.cc BUG#45674 FLUSH STATUS does not reset semisynchronous counters 2009-10-12 21:03:04 +08:00
semisync_slave.cc Backport BUG#45848 Semisynchronous replication internals are visible in SHOW PROCESSLIST and logs 2009-10-12 20:55:01 +08:00
semisync_slave.h Backport BUG#45848 Semisynchronous replication internals are visible in SHOW PROCESSLIST and logs 2009-10-12 20:55:01 +08:00
semisync_slave_plugin.cc Backport Bug#45852 Semisynch: Last_IO_Error: Fatal error: Failed to run 'after_queue_event' hook 2009-10-12 20:57:30 +08:00