Nice reply.
On Fri, Apr 4, 2008 at 5:19 PM, Krishna Chandra Prajapati <
[EMAIL PROTECTED]> wrote:
> Master-->Slave1/Master>Slave2 (Chain 1
> to 1)
> Slave1 should have --log_slave_updates
>
>
> Master->Slave1/Slave2/Slave3.
>
thank u very much
On 4/4/08, Krishna Chandra Prajapati <[EMAIL PROTECTED]> wrote:
>
> Master-->Slave1/Master>Slave2 (Chain 1
> to 1)
> Slave1 should have --log_slave_updates
>
>
> Master->Slave1/Slave2/Slave3.
> (Parallel 1 to
Master-->Slave1/Master>Slave2 (Chain 1
to 1)
Slave1 should have --log_slave_updates
Master->Slave1/Slave2/Slave3.
(Parallel 1 to many)
--log_slave_updates is not required
If all the slaves are in a single chain model then --
so, we should not have --log-slave-update on slaves on setup with one master
and multiple slaves...right.
regards
anandkl
On 4/4/08, Krishna Chandra Prajapati <[EMAIL PROTECTED]> wrote:
>
> In case of master is down. Slave 1 has to be made as master and
> --log_slave_updates has to be removed. S
In case of master is down. Slave 1 has to be made as master and
--log_slave_updates has to be removed. Slave2 will act as slave. There will
be no "duplicate key"
On Thu, Apr 3, 2008 at 1:02 PM, Ananda Kumar <[EMAIL PROTECTED]> wrote:
> But, it also says, that if slave1 is made master and if log-s
But, it also says, that if slave1 is made master and if log-slave-update is
set on it, then
slave2 might receive data that it might have arleady got from the old
master, which might cause errors like "duplicate keys" etc.
On 4/3/08, Krishna Chandra Prajapati <[EMAIL PROTECTED]> wrote:
>
> Hi,
> T
Hi,
There is nothing that, you can not enable log_slave_updates on slave.
Basically, it is useful in a situation when you have 1 master and 2 or more
slave in chain series. In this model 1st slave server should work as master
as well as slave. So, log_slave_update and binlog can be enabled to log
