Sam,
On Fri, Aug 22, 2003 at 08:37:33PM -0400, sam [EMAIL PROTECTED] wrote:
> So, you are saying that the fact that replication is
> not working when we re-connect is not a bug.
>
> Replication is all about passing data from one node
> (a master) to the next (the slave). I do not know what
> it
Alexander,
Friday, November 01, 2002, 2:02:18 PM, you wrote:
AB> Every time I want to replicate, do I have to restart?
No. Use SLAVE START and SLAVE STOP commands.
--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.net http://www.ensi
On Friday 28 December 2001 10:18 am, Steve Rapaport wrote:
> I didn't think it was possible to put arbitrary mysql commands like SHOW
> MASTER STATUS into a script. ?I had assumed I was limited to the
> shell-level utilities like mysqlimport and mysqldump.
> How exactly do I put the
> interactiv
>>How do we automatically know the master has failed and record that offset?
>>
>
> You need to have your system set up in such a way that failover event will
> trigger the execution of a script, which will do all the magic.
Good idea!
I didn't think it was possible to put arbitrary mysql com
> > Here is how you can do the above:
> >
> > * make sure slave runs with log-bin.
> >
> > * before you direct updates to the slave, record the binlog offset and
> > position on the slave by running SHOW MASTER STATUS ( on the slave not on
the
> > master!)
>
>
> Whoops! When the failover
Sasha, thanks for your help!
But I'm not sure we're in agreement about what
is happening yet:
Sasha Pachev wrote:
> On Wednesday 26 December 2001 01:24 pm, Venu wrote:
>
>>Since replication is only one-way, there really shouldn't be any updates
>>happening on the slave, but in the failover ca
