Re: fwd: Bugs in replication ? (binlog-do-db, replicate-rewrite-db)

> Hi,
>
> I dont want to "stress" this listing, but as far as I have tested I cannot find any other solution then this could be a bug too in replication.
>
> Configuration is Win2000 Server (fully patched), MySQL 4.0.12 on both master and slave.
>
> The replication are working, binary files are "copyed" from master to slave, and updates takes place.
>
> When adding some of the master-commands from 4.10.5, like "binlog-do-db" on the master, the master stops collecting binary-files.
>
> When adding some of the slave-commands from 4.10.5, like "replicate-rewrite-db" the slave stops updating, but binary-files are "copyed" to the slave.
>
> For my last testing, the FLUSH LOGS have been used between each step for checking, and both SHOW MASTER STATUS and SHOW SLAVE STATUS shows that master and slave are syncronized on positions in the binary files - step-by-step.
>
> Taking off the special master/slave commands, replication are back again.

Hi again,

Please first re-read the section about binlog-do-db and replicate-rewrite-db
in our online manual (it may be more detailed than the manual that shipped with
4.0.12, as I frequently update the manual).
The most frequent mistake users make is do cross-database updates
(use db1; update db2.t set a=10 where a=5), this does not work with
binlog-do-db and replicate-rewrite-db (see the manual).
Another mistake is forgetting that binlog-do-db excludes all not
mentioned databases from replication.

--
For technical support contracts, visit https://order.mysql.com/?ref=mgbi
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Guilhem Bichot
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Software Developer
/_/ /_/\_, /___/\___\_\___/ Bordeaux, France
<___/ www.mysql.com



--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org

Re: fwd: Bugs in replication ? (binlog-do-db, replicate-rewrite-db)

Hi Guilhem,

I will try again, but I think I have studied any issues Google can bring up
on this subject.

The issue is, that the "my.ini" replication-setup in both master and slave
has been running on MySQL 3.23.49 for apx. six month now - so I did not
expected that big change when upgrading to 4.0.12.

Best regards
Peter


----- Original Message -----
From: "Guilhem Bichot"
To:
Cc:
Sent: Thursday, May 01, 2003 10:38 PM
Subject: Re: fwd: Bugs in replication ? (binlog-do-db, replicate-rewrite-db)


> > Hi,
> >
> > I dont want to "stress" this listing, but as far as I have tested I
cannot find any other solution then this could be a bug too in replication.
> >
> > Configuration is Win2000 Server (fully patched), MySQL 4.0.12 on both
master and slave.
> >
> > The replication are working, binary files are "copyed" from master to
slave, and updates takes place.
> >
> > When adding some of the master-commands from 4.10.5, like "binlog-do-db"
on the master, the master stops collecting binary-files.
> >
> > When adding some of the slave-commands from 4.10.5, like
"replicate-rewrite-db" the slave stops updating, but binary-files are
"copyed" to the slave.
> >
> > For my last testing, the FLUSH LOGS have been used between each step for
checking, and both SHOW MASTER STATUS and SHOW SLAVE STATUS shows that
master and slave are syncronized on positions in the binary files -
step-by-step.
> >
> > Taking off the special master/slave commands, replication are back
again.
>
> Hi again,
>
> Please first re-read the section about binlog-do-db and
replicate-rewrite-db
> in our online manual (it may be more detailed than the manual that shipped
with
> 4.0.12, as I frequently update the manual).
> The most frequent mistake users make is do cross-database updates
> (use db1; update db2.t set a=10 where a=5), this does not work with
> binlog-do-db and replicate-rewrite-db (see the manual).
> Another mistake is forgetting that binlog-do-db excludes all not
> mentioned databases from replication.
>
> --
> For technical support contracts, visit https://order.mysql.com/?ref=mgbi
> __ ___ ___ ____ __
> / |/ /_ __/ __/ __ \/ / Mr. Guilhem Bichot
> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Software Developer
> /_/ /_/\_, /___/\___\_\___/ Bordeaux, France
> <___/ www.mysql.com
>
>
>


--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org

Re: fwd: Bugs in replication ? (binlog-do-db, replicate-rewrite-db)

Hi,

Indeed, if it was working with 3.23.49 and does not after a simple
upgrade to 4.0.12, it's not normal.
Are your master and slave both 4.0.12 ? A 3.23 master cannot
replicate a 4.0 slave.
If you have a testcase I'm interested in it.
Testcase should be of the form:

"with these options, I do these commands and this happens;
then I shutdown the slave, restart without these options, I do
these commands and this happens."

If you have such a testcase, please include my.ini (master and slave)
and output of SHOW SLAVE STATUS (on the slave) and SHOW MASTER STATUS
(on the master) after startup and after every command.

Thanks.

PeterWR wrote:
> Hi Guilhem,
>
> I will try again, but I think I have studied any issues Google can bring up
> on this subject.
>
> The issue is, that the "my.ini" replication-setup in both master and slave
> has been running on MySQL 3.23.49 for apx. six month now - so I did not
> expected that big change when upgrading to 4.0.12.
>
> Best regards
> Peter
>
>
> ----- Original Message -----
> From: "Guilhem Bichot"
> To:
> Cc:
> Sent: Thursday, May 01, 2003 10:38 PM
> Subject: Re: fwd: Bugs in replication ? (binlog-do-db, replicate-rewrite-db)
>
>
>
>>>Hi,
>>>
>>>I dont want to "stress" this listing, but as far as I have tested I
>
> cannot find any other solution then this could be a bug too in replication.
>
>>>Configuration is Win2000 Server (fully patched), MySQL 4.0.12 on both
>
> master and slave.
>
>>>The replication are working, binary files are "copyed" from master to
>
> slave, and updates takes place.
>
>>>When adding some of the master-commands from 4.10.5, like "binlog-do-db"
>
> on the master, the master stops collecting binary-files.
>
>>>When adding some of the slave-commands from 4.10.5, like
>
> "replicate-rewrite-db" the slave stops updating, but binary-files are
> "copyed" to the slave.
>
>>>For my last testing, the FLUSH LOGS have been used between each step for
>
> checking, and both SHOW MASTER STATUS and SHOW SLAVE STATUS shows that
> master and slave are syncronized on positions in the binary files -
> step-by-step.
>
>>>Taking off the special master/slave commands, replication are back
>
> again.
>
>>Hi again,
>>
>>Please first re-read the section about binlog-do-db and
>
> replicate-rewrite-db
>
>>in our online manual (it may be more detailed than the manual that shipped
>
> with
>
>>4.0.12, as I frequently update the manual).
>>The most frequent mistake users make is do cross-database updates
>>(use db1; update db2.t set a=10 where a=5), this does not work with
>>binlog-do-db and replicate-rewrite-db (see the manual).
>>Another mistake is forgetting that binlog-do-db excludes all not
>>mentioned databases from replication.
>>
>>--
>>For technical support contracts, visit https://order.mysql.com/?ref=mgbi
>> __ ___ ___ ____ __
>> / |/ /_ __/ __/ __ \/ / Mr. Guilhem Bichot
>> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Software Developer
>>/_/ /_/\_, /___/\___\_\___/ Bordeaux, France
>> <___/ www.mysql.com
>>
>>
>>
>
>
>


--
For technical support contracts, visit https://order.mysql.com/?ref=mgbi
Are you MySQL certified? visit http://www.mysql.com/certification/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Guilhem Bichot
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Software Developer
/_/ /_/\_, /___/\___\_\___/ Bordeaux, France
<___/ www.mysql.com


--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org