Hello list,
I'm in the phase of upgrading mysql from 3.23(.58) to 4.0(.23). I have
some replication setups. Following the manual, the upgrade process went
very smooth.
Now I have some problems with checking replication automatically. For
3.23 I wrote a shell script, that looks on the master for the Binlog
Dump Processes in "show processlist;". That worked perfectly. If the
replication was disrupted, the respective process was gone immediately
and the check script could send a warning. Principally, the same check
script works for 4.0.23, too, but if I stop a slave, the respective
Binlog Dump Process vanishes not immediately from the master. It lasts
2200 to 2600 seconds, before the process is gone. Even if I shut down
the whole slave server, the Binlog Dump Process stays in the
processlist. I haven't found a variable to shorten these 2200 to 2600
seconds to a shorter period of time.
With this experience, I tried to setup report-host on the slave side
and check on the master with "show slave hosts;". This works also as
the method above: If slave is disconnected, the respective slave stays
in the list of "show slave hosts;". Only after a longer period of time,
the slave vanished from the list.
OK, I could write a script to check replication on the slave side. But
I did this some times ago (on 3.23). The result was, that in some
cases, the script ("show slave status;" also) reported a running slave,
which wasn't the truth. So I wouldn't trust this method.
Is there a possibility to check replication on the master side?
For answers I thank you very much.
Best Regards
Kurt Tragant
