On Thu, Aug 26, 2010 at 6:04 AM, Norman Khine wrote:
> hello,
> i have a working master-slave replication, the problem i find is that
> if i restart the MASTER there is a difference in the MASTER_LOG_FILE
> and MASTER_LOG_POS on the SLAVE.
>
> what is the correct way to keep the two slaves in sync
* 1. row ***
Slave_IO_Running: Yes
Slave_SQL_Running: Yes
-Original Message-
From: Norman Khine [mailto:nor...@khine.net]
Sent: Thursday, August 26, 2010 6:05 AM
To: mysql@lists.mysql.com
Subject: master-slave replication sync proble
Slave_IO_Running: Yes
Slave_SQL_Running: Yes
> -Original Message-
> From: Norman Khine [mailto:nor...@khine.net]
> Sent: Thursday, August 26, 2010 6:05 AM
> To: mysql@lists.mysql.com
> Subject: master-slave replication sync problems.
>
> hello,
> i have a wor
Quoting jitendra ranjan :
Hi,
The best way to use sync the master and slave is using mk-checksum
tools. just google it and use the the tools for online sync of
master and slave.
Jeetendra Ranjan
MySQL DBA
Yes, data integrity isnt guaranteed with MySQL replication. So if you
want to b
Quoting Ananda Kumar :
Smith,
I never said, this wont work.Some times, there are chances of lossing data.
regards
anandkl
If you have experience of this fair enough. Theres no reason it should
make any difference, as everything is based upon the binlog file and
position...
--
MySQL
Hi,
The best way to use sync the master and slave is using mk-checksum tools. just
google it and use the the tools for online sync of master and slave.
Jeetendra Ranjan
MySQL DBA
--- On Thu, 26/8/10, Norman Khine wrote:
From: Norman Khine
Subject: master-slave replication sync problems
Smith,
I never said, this wont work.Some times, there are chances of lossing data.
regards
anandkl
On Thu, Aug 26, 2010 at 8:48 PM, wrote:
> Quoting Norman Khine :
>
> i see, so the best is to just stop slave and then check the master
>> status, and when the master status syncs then i start t
Quoting Norman Khine :
i see, so the best is to just stop slave and then check the master
status, and when the master status syncs then i start the slave?
Well Im willing to hear from others experiences, but if you really
shouldnt have to do anything. If you want you can issue a stop slav
Yes,
You need to note down the master bin-log file name and position on the
slave, this is a must.
regards
anandkl
On Thu, Aug 26, 2010 at 7:34 PM, Norman Khine wrote:
> i see, so the best is to just stop slave and then check the master
> status, and when the master status syncs then i start
i see, so the best is to just stop slave and then check the master
status, and when the master status syncs then i start the slave?
On Thu, Aug 26, 2010 at 3:09 PM, wrote:
> That is really bad, you will loose changes.
>
> You shouldnt have to do anything when rebooting either the master or sla
True,
But some times, this does not work and u need to know the master bin-log
file and position to start, so that there is no loss of data.
regards
anandkl
On Thu, Aug 26, 2010 at 6:39 PM, wrote:
> That is really bad, you will loose changes.
>
> You shouldnt have to do anything when rebooting
That is really bad, you will loose changes.
You shouldnt have to do anything when rebooting either the master or
slave. If the master is down, then the slave recieves no updates. If
the slave is down, when it comes back up it checks the master log pos
and plays thro any changes that are nec
since u r starting slave by postion beyond master, and if some of the
changes are already present on slave, it would error out with duplicate.
You need
show slave status\G;
slave stop;
show slave status\G;..wait for few min..than again
show slave status\G;just to make sure...slave is in comple
hello,
i have a working master-slave replication, the problem i find is that
if i restart the MASTER there is a difference in the MASTER_LOG_FILE
and MASTER_LOG_POS on the SLAVE.
what is the correct way to keep the two slaves in sync even after i
restart the server. the way i do it now is to:
[MA
14 matches
Mail list logo
