List:Replication« Previous MessageNext Message »
From:Database System Date:March 17 2010 3:24pm
Subject:Fw: Re: master to master replication broke
View as plain text  
If you had read carefully, you would know the reason cannot connect to server because
admin rebooted the server hosts.
I knew change master to current position is not a good solution, I just want to see if
replication can be resumed. In fact, after that it is still stopped on where it was before
broken. It didn't changed to new position.

--- On Wed, 3/17/10, Johan De Meersman <vegivamp@stripped> wrote:

From: Johan De Meersman <vegivamp@stripped>
Subject: Re: master to master replication broke
To: database100@stripped
Cc: replication@stripped
Date: Wednesday, March 17, 2010, 10:13 AM

On Wed, Mar 17, 2010 at 4:00 PM, Database System <database100@stripped> wrote:


I have master to master replication ran was fine. One time admin re-booted one host and
followed rebooted another one. After that, one of the masters was able to automatically
re-connect to master and continue replication, but another master caould not resume

I did three things and all got same error message on the screen. (1. re-started slave;
2.change master to where it was stopped; 3. change master to current log file and
position). The error message is:

ERROR 1201 Could not initialize master info structure; more error messages can be found in
the MySQL error log.

In the error log, it only said cannot connect to sserver... Error reading relay log...
read up to .... SQL thread killed ... Normal shutdown
this log is the same as in another master and that server was able to re-connect.

Any idea of how to recover the replication without dump and sync database?

Congratulations. By doing "3. change master to current log file and position", you
*almost* condemned yourself to the dump/sync you dread.

You're actually lucky that it didn't start replicating when you did that. Hurry up and put
it back to the original settings, before you do anything else - if a single statement gets
executed, you're screwed.

As to what's wrong, I would think "cannot connect to server" is pretty obvious. Find out
*why*. Hint: try to telnet into the IP/port configured in your mysql slave.

Bier met grenadyn
Is als mosterd by den wyn
Sy die't drinkt, is eene kwezel
Hy die't drinkt, is ras een ezel

Fw: Re: master to master replication brokeDatabase System17 Mar
  • Re: Fw: Re: master to master replication brokeJohan De Meersman17 Mar