24 messages in com.mysql.lists.bugsShutting down one server, creates a n...
FromSent OnAttachments
Melvyn Sopacua28 May 2002 07:29 
Sasha Pachev29 May 2002 14:09 
Melvyn Sopacua19 Aug 2002 02:46 
Michael Widenius19 Aug 2002 12:33 
Melvyn Sopacua19 Aug 2002 16:56 
Fredrick Bartlett19 Aug 2002 18:59 
Sinisa Milivojevic20 Aug 2002 08:47 
Fredrick Bartlett20 Aug 2002 15:33 
Fredrick Bartlett20 Aug 2002 19:59 
Jani Tolonen21 Aug 2002 03:01 
Fredrick Bartlett02 Sep 2002 17:30 
Michael Widenius03 Sep 2002 06:06 
Melvyn Sopacua09 Sep 2002 11:38 
Sinisa Milivojevic09 Sep 2002 11:50 
Melvyn Sopacua09 Sep 2002 12:01 
Colin Faber09 Sep 2002 12:04 
Sinisa Milivojevic10 Sep 2002 04:29 
Michael Widenius10 Sep 2002 11:40 
Peter Zaitsev17 Sep 2002 22:28 
Melvyn Sopacua21 Sep 2002 15:24 
Peter Zaitsev25 Sep 2002 04:26 
Michael Widenius26 Sep 2002 11:50 
Michael Widenius26 Sep 2002 11:53 
Melvyn Sopacua27 Sep 2002 01:32 
Subject:Shutting down one server, creates a new logfile every few seconds
From:Melvyn Sopacua (md@idg.nl)
Date:05/28/2002 07:29:03 AM
List:com.mysql.lists.bugs

Description:

When one of the servers in a replication scheme, where master = slave of
master, goes down, the servers replicate eachothers 'set logfile' command. This results in a new logfile being created every few seconds and tying up
server resources.

How-To-Repeat:

1) Set up a tipical replication scheme, where the master of x is also the slave
of x and vice-versa. 2) Make sure replication is working. 3) Shutdown one of the servers.

Notice, the number of logfiles in the logdirectory.

I am unsure if this is related to the use of the
log-bin=/path/to/logdir/logname directive.

Fix:

Work-around: stop the slave, before a shutdown. This is only a marginal
work-around, cause if a server crashes, for whatever reason, this can also happen.

Submitter-Id: <submitter ID> Originator: MelvynSopacua Organization: IDG.nl MySQL support: none Synopsis: set logfile command is replicated Severity: critical Priority: high Category: mysql Class: sw-bug Release: mysql-4.0.1-alpha (AIX Production Version, as of Sun, 28 Apr 2002) Server: /data/mdev/mysql/bin/mysqladmin Ver 8.23 Distrib 4.0.1-alpha, for
ibm-aix4.3.3.0 on rs6000

Copyright (C) 2000 MySQL AB & MySQL Finland AB & TCX DataKonsult AB This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to modify and redistribute it under the GPL license

Server version 4.0.1-alpha-log Protocol version 10 Connection Localhost via UNIX socket UNIX socket /data/mdev/sql/tmp/mysql4.sock Uptime: 3 min 55 sec

Threads: 2 Questions: 21 Slow queries: 1 Opens: 10 Flush tables: 1 Open
tables: 4 Queries per second avg: 0.089

Environment:

System: AIX femke 3 4 0044CA0A4C00

Some paths: /bin/perl /home/mdev/local/bin/make /home/mdev/local/bin/gmake
/usr/local/bin/gcc /home/mdev/bin/cc GCC: Reading specs from
/usr/local/lib/gcc-lib/powerpc-ibm-aix4.3.2.0/2.95.2.1/specs gcc version 2.95.2.1 19991024 (release) Compilation info: CC='gcc -pipe -mcpu=power -Wa,-many' CFLAGS='' CXX='gcc
-pipe -mcpu=power -Wa,-many' CXXFLAGS='-felide-constructors -fno-exceptions
-fno-rtti' LDFLAGS='' LIBC: lrwxrwxrwx 1 bin bin 19 May 14 2001 /lib/libc.a ->
/usr/ccs/lib/libc.a lrwxrwxrwx 1 bin bin 19 May 14 2001 /usr/lib/libc.a ->
/usr/ccs/lib/libc.a Configure command: ./configure --prefix=/data/mdev/mysql
--localstatedir=/data/mdev/sql/var --with-raid
--with-unix-socket-path=/data/mdev/sql/tmp/mysql.sock --with-port=3406
--with-mysqld-user=mdev --without-debug '--with-comment=AIX Production Version,
as of Sun, 28 Apr 2002' --without-bench --with-charset=latin1
--with-extra-charsets=none --without-isam --with-berkeley-db

ADDITIONAL INFO: 020528 16:16:14 Slave: received 0 length packet from server, apparent master
shutdown: (0) 020528 16:16:14 Slave: Failed reading log event, reconnecting to retry, log
'rep_log.001' position 42519 020528 16:16:14 Slave thread: error connecting to master: , last_errno=1159,
retry in 60 sec 020528 16:17:14 Slave: connected to master
'replicate@192.168.101.120:3406',replication resumed in log 'rep_log.001' at
position 42519 020528 16:18:52 Slave thread killed while reading event 020528 16:18:52 Slave thread exiting, replication stopped in log 'rep_log.1625'
at position 4

Notice the last line: rep_log.1625 in under 2 minutes.