hi guys,
we have a mysql replication setup in our production.
Master: mysql-5.0.77
slave: mysql-5.1.46
Recently, slave show many these kind of issues and SQL thread was stopped:
Last_SQL_Error: Error 'No data - zero rows fetched, selected, or
processed' on query. Default
Hello.
I have mysql-4.1.14 and 4.1.15 on PLD's.
When the Slave_IO_State is in 'Connecting to Master' state
because of the unreachable master host (timeouting)
the 'slave stop' or 'slave stop io_thread' tooks
minimum 2 minutes.
fe.:
mysql stop slave io_thread;
Query OK, 0 rows affected (2 min
(timeouting)
the 'slave stop' or 'slave stop io_thread' tooks
minimum 2 minutes.
fe.:
mysql stop slave io_thread;
Query OK, 0 rows affected (2 min 52.11 sec)
the processlist when waiting for death of thread:
*** 1. row
Carl,
- Original Message -
From: Carl McNamee [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Tuesday, December 10, 2002 6:36 AM
Subject: RE: Question about SLAVE STOP
I know that the slave will honor transactions but how does that effect the
STOP SLAVE command? Based
it will roll
back.
Correct. The change of 3.23.52 was what was needed to make SLAVE STOP
honor (full) transactions.
I'm also assuming that the pointer for the bin-log will now point to
the begining of the transaction that was rolled back.
Unfortunately no. This what my last remark (in the other mail
: Question about SLAVE STOP
Hello.
On Sat 2002-12-07 at 14:26:00 +0100, [EMAIL PROTECTED] wrote:
Hello.
On Fri 2002-12-06 at 16:13:54 -0600, [EMAIL PROTECTED]
wrote:
First off, we are using Innodb tables on version 3.23.53a-max.
If the command STOP SLAVE is issued in the middle
Hi!
- Original Message -
From: Benjamin Pflugmann [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Saturday, December 07, 2002 4:59 PM
Subject: Re: Question about SLAVE STOP
Hello.
On Sat 2002-12-07 at 14:26:00 +0100, [EMAIL PROTECTED] wrote:
Hello.
On Fri 2002-12-06
Hi!
I was able to break replication with a single SLAVE STOP command in 4.0.6.
I ran an InnoDB stress test ibtest17.
From the printout below we see that after SLAVE START immediately we got a
foreign key error in the slave. That shows the slave no longer was identical
to the master, since only
Hello.
On Fri 2002-12-06 at 16:13:54 -0600, [EMAIL PROTECTED] wrote:
First off, we are using Innodb tables on version 3.23.53a-max.
If the command STOP SLAVE is issued in the middle of the following type of
transaction:
set autocommit = 0;
update...;
update...;
update...;
commit;
Hello.
On Sat 2002-12-07 at 14:26:00 +0100, [EMAIL PROTECTED] wrote:
Hello.
On Fri 2002-12-06 at 16:13:54 -0600, [EMAIL PROTECTED] wrote:
First off, we are using Innodb tables on version 3.23.53a-max.
If the command STOP SLAVE is issued in the middle of the following type of
sql,query
First off, we are using Innodb tables on version 3.23.53a-max.
If the command STOP SLAVE is issued in the middle of the following type of
transaction:
set autocommit = 0;
update...;
update...;
update...;
commit;
does it roll back the current transaction or wait for it to complete?
: Tuesday, November 12, 2002 4:59 AM
Subject: Re: SLAVE STOP
At 08:02 11/11/2002 +0100, Massimo Petrini wrote:
Hi,
Thanks for your bug the report. I was be able to repeat the
same behavior running two services on the same Win2k machine.
However testing I found that using the port=3307 for the master
Massimo,
Tuesday, November 19, 2002, 12:35:46 PM, you wrote:
MP In the 4.0.5 version the problem is still alive. Have some notice about this
MP problem will be solved ?
This bug is not fixed yet, we gonna fix it later.
--
For technical support contracts, goto
Pada Mon, 11 Nov 2002 08:02:31 +0100
Massimo Petrini [EMAIL PROTECTED] menulis:
Good morning to all
On mysql 4,0,4 running under W2K SP3, when I run the command SLAVE STOP;
the
command it is not execute and it remain pending (the prompt of mysql
doesn't
return); instead all is normal
| 3306 |
| protocol_version | 10|
+--+---+
3 rows in set (0.00 sec)
I was be able to perform the command:
mysql slave stop;
Query OK, 0 rows affected (0.00 sec)
Of course, that the reason why will be analyzed and fixed
Good morning to all
On mysql 4,0,4 running under W2K SP3, when I run the command SLAVE STOP;
the
command it is not execute and it remain pending (the prompt of mysql
doesn't
return); instead all is normal under 3.53.
Which is the problem ?
tks regards
On mysql 4,0,4 running under W2K SP3, when I run the command SLAVE STOP; the
command it is not execute and it remain pending (the prompt of mysql doesn't
return); instead all is normal under 3.53.
Which is the problem ?
tks regards
Description:
Deadlock occurs when slave is locked trying to write to table that was
write locked by separate process who then tries to do a slave stop. This should
only happen on a mutual master set up (i.e. 2 servers that are each other's
master); otherwise, the only write locks would
Description:
If a 'slave stop' command is while a slave is blocked waiting
for a table, the slave thread must be manually killed in order for the
slave stop command to complete.
How-To-Repeat:
mysql show slave status\G
*** 1. row
Hi there
When issuing this command it seems like MYSQL process hangs. The server
still responds, etc etc but the process that issued that command says
waiting for slave to die and that takes a long time, eventually after 20
minutes I just disconnected the two servers and the process continued
20 matches
Mail list logo
