diff options
| author | He Zhenxing <zhenxing.he@sun.com> | 2009-10-12 20:55:01 +0800 |
|---|---|---|
| committer | He Zhenxing <zhenxing.he@sun.com> | 2009-10-12 20:55:01 +0800 |
| commit | f8155de07828c4fdbe1e3ec2b7e0915cfa26e462 (patch) | |
| tree | 0f1ff7d4db0e95f267665506c40a22068fe849c8 /INSTALL-WIN-SOURCE | |
| parent | d8724a4538a61ea6f98fb770c951b89bde734f77 (diff) | |
| download | mariadb-git-f8155de07828c4fdbe1e3ec2b7e0915cfa26e462.tar.gz | |
Backport BUG#45848 Semisynchronous replication internals are visible in SHOW PROCESSLIST and logs
Semi-sync uses an extra connection from slave to master to send
replies, this is a normal client connection, and used a normal
SET query to set the reply information on master, which is visible
to user and may cause some confusion and complaining.
This problem is fixed by using the method of sending reply by
using the same connection that is used by master dump thread to
send binlog to slave. Since now the semi-sync plugins are integrated
with the server code, it is not a problem to use the internal net
interfaces to do this.
The master dump thread will mark the event requires a reply and
wait for the reply when the event just sent is the last event
of a transaction and semi-sync status is ON; And the slave will
send a reply to master when it received such an event that requires
a reply.
Diffstat (limited to 'INSTALL-WIN-SOURCE')
0 files changed, 0 insertions, 0 deletions