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
Hello List,
On 8/26/2010 3:00 PM, Daevid Vincent wrote:
ssh to the slave
mysql -uroot -pPASSWORD -P3306 -hlocalhost
show slave status\G
If the Slave IO is NOT Running, but SQL is, then simply try to restart the
slave...
*** 1. row ***
ssh to the slave
mysql -uroot -pPASSWORD -P3306 -hlocalhost
show slave status\G
If the Slave IO is NOT Running, but SQL is, then simply try to restart the
slave...
*** 1. row ***
Slave_IO_State:
Master_Host: 10.10.10.45
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.
T
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
> from what i've read and seen geographical load balancer
> works as: multiple DNS A records routes to multiple
> Apache Servers(mod_php tucks in as a module under Apache)
> each web servers would connect to MySQL on their own
> localhost 1.2.3.4-WebServer would communicate directly to
> 1.2.3.4-M
> Do you want geographic redundancy or do you want to scale reads?
> In this case you're talking about scaling reads for a bunch of
> apps all running together. If you want performance in that case,
> then first you'd want to isolate the apps from each other.
Geographic redundancy is my primary g
25, 2009 4:18 PM
To: Gavin Towey
Cc: mysql@lists.mysql.com
Subject: Re: Master/Slave Replication Question
> Moreover, it works today as opposed to waiting until the end
> of time for the database developers to add features like that
> (which mysql cluster is already a distributed database
> Moreover, it works today as opposed to waiting until the end
> of time for the database developers to add features like that
> (which mysql cluster is already a distributed database, and
> the devs have said they're not interested in trying to turn
> the regular mysql into a distributed product,
ey were designed to scale well.
Regards,
Gavin Towey
-Original Message-
From: Tim Gustafson [mailto:t...@soe.ucsc.edu]
Sent: Friday, September 25, 2009 2:44 PM
To: mysql@lists.mysql.com
Subject: Re: Master/Slave Replication Question
> Another thought would be at the application laye
> Another thought would be at the application layer, sending
> all the updates (insert,delete, update, etc) to server A,
> and the selects to the local slave servers.
This has been suggested before, and I'm totally against it. Applications like
PHPBB, Drupal, WordPress, etc can't be easily confi
On Thu, May 22, 2008 at 5:36 PM, Salah Nait-Mouloud <
[EMAIL PROTECTED]> wrote:
> Hi all.
>
> I have 2 MySQL servers.
> One master and one slave.
> In order to add new slave server, and because i can't stop the master one,
> i
> have tried this:
>
> http://forums.mysql.com/read.php?26,99846,102058
Hi Tom,
Your master binary log start with mysql-bin.03, then, your insert ( or
update) in the master could be in mysql-bin.02 or 1.
Please, reload your binary logs again from the beginning ( put
mysql-bin.02 or 1, ). Your insert or update could be in one of this
files.
Regards,
Juan
Yes thanks - i have done that and restarted the slave and _some_
tables now appear to update but others dont
eg
master:
mysql> select count(*) from tbl_checkcommand;
+--+
| count(*) |
+--+
| 30 |
+--+
1 row in set (0.00 sec)
slave:
mysql> select count(*) from
The error 1062 you could skipped in the slave modifying your my.cnf ( slave
side) using :
slave-skip-errors=1062
This error on duplicated records, normally is problem in binarylogs transfer
data. But, anyway, please confer that the data exist in the slave.
Yes thanks - i have done tha
Hi Tom,
The error 1062 you could skipped in the slave modifying your my.cnf ( slave
side) using :
slave-skip-errors=1062
This error on duplicated records, normally is problem in binarylogs transfer
data. But, anyway, please confer that the data exist in the slave.
Regards,
Juan
On Fri, May
bruce wrote:
hi..
doing a simple test of master/slave replication, using mysql.
i have two test systems:
master - foo (192.168.10.13)
slave - cat (192.168.20.20)
on both machines, i created a testmasterdb. on the master, i populated the
tbl within the db with some test data. there are no
At 14:11 -0400 10/18/03, DePhillips, Michael P wrote:
Hi List
I'm having trouble start a slave. All seems to be configured well as per
show slave status, I issue a
mysql> slave start;
Query OK, 0 rows affected (0.00 sec)
and nothing happens, show slave status sill says slave is not running.
Any
Got it to work after the restart. Now works fine.
SO now back to the Master-Master replication
Dathan Vance Pattishall <[EMAIL PROTECTED]> wrote:
Type show slave status to figure out what the problem is on the slave.
Type show full processlist on the master to see if the slave is
connecte
Type show slave status to figure out what the problem is on the slave.
Type show full processlist on the master to see if the slave is
connected waiting for binlog updates.
Make sure the master is replicating..
Etc.
-->-Original Message-
-->From: Sanya Shaik [mailto:[EMAIL PROTECTED]
--
Here is a good URL, maybe it can help you to deploy your Master-Slave
solution.
URL: http://mysql.us.themoes.org/doc/en/Replication_HOWTO.html
Greetings
Mikel
From: Sanya Shaik <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Master-Slave Replication Date: Thu, 21 Aug 2003 12:50:31 -0700
(PD
29 matches
Mail list logo
