On Wed, Apr 28, 2010 at 12:17 AM, Kandy Wong kan...@triumf.ca wrote:
Is it true that the performance of running a query on a live replication
master and slave has to be much slower than running a query on a static
server?
I've tried to run the following query on a replication master
Hi,
Is it true that the performance of running a query on a live replication
master and slave has to be much slower than running a query on a static
server?
I've tried to run the following query on a replication master and it
takes 1 min 13.76 sec to finish.
SELECT *, ABS(timeA-1266143632
Hi Eric,
At least with Maatkit, you get transparency. We make a concerted
effort to update the RISKS section of each tool with each release, so
there
is full disclosure.
Fair enough, but I still found the warnings a little too scary. A more
complete explanation of the exact nature of the
about triggering them
would have increased my comfort level.
I think Maatkit is by far the best solution for live master-slave sync
in most real-world situations.
We'll give it another look.
--
Eric Robinson
Disclaimer - December 9, 2009
This email and any files transmitted
disclosure.
I think Maatkit is by far the best solution for live master-slave sync
in most real-world situations.
- Baron
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Let's face it, sometimes the master and slave get out of sync, even when
'show slave status' and 'show master status' indicate that all is well.
And sometimes it is not feasible to wait until after production hours to
resync them. We've been working on a method to do an emergency
hot-resync
i have two questions. (1) innodb? (2) why delete slave logs when you can
restart the slave with --skip-slave and then use CHANGE MASTER TO?
tom
On 12/4/09 6:34 AM, Robinson, Eric eric.robin...@psmnv.com wrote:
Let's face it, sometimes the master and slave get out of sync, even when
'show
(1) innodb?
It's an off-the-shelf application that uses MyISAM tables. It is
possible to convert to innodb, but I have not been sold on innodb in
terms of its performance characteristics for this particular
application. Maybe I've been reading the wrong stuff. Do you have
general thoughts on
On 12/4/09 11:59 AM, Robinson, Eric eric.robin...@psmnv.com wrote:
(2) why delete slave logs when you can
restart the slave with --skip-slave and
then use CHANGE MASTER TO?
Well... I guess mainly because I didn't know about that option! I
thought I needed to fake out mysql on this, but it
I think he's trying to say that this method wouldn't work for innodb, unless
you copied files from an LVM snapshot, or something similar.
I would say that it's very important to know why data is getting out of sync
between your master and slave. Fixing those root causes would eliminate
On 12/4/09 3:14 PM, Gavin Towey gto...@ffn.com wrote:
I would say that it's very important to know why data is getting out of sync
between your master and slave. Fixing those root causes would eliminate the
need for this.
i very much agree. the only instances of slaves getting out of whack
I would say that it's very important to know why data
is getting out of sync between your master and slave.
Ultimately, I agree. But since it's a canned application, getting to
that point might be hard, and once it is resolved, new issues might
arise. I would never have any confidence
Message-
From: Robinson, Eric [mailto:eric.robin...@psmnv.com]
Sent: Friday, December 04, 2009 1:24 PM
To: Gavin Towey; Tom Worster; mysql@lists.mysql.com
Subject: RE: Here's an Idea for Re-Syncing Master and Slave During Production
Hours without Interrupting Users (Much)
I would say that it's very
I would never have any confidence that the replication
is solid enough to use the slave server for backup purposes.
I agree completely there. That's the other reason I like filesystem
snapshots is that it allows you to take a backup from
the master relatively painlessly.
I've thought of
I have successfully set up a replication master/slave scenario with my MySQL
5.0.51a
Now in the event of a fail over to the slave (an identical appliance), I want
the old master to become the slave for an eventual switch back the other way.
Would it really take the same process to keep the old
both writable.
-Aaron
On Wed, Jul 8, 2009 at 1:38 PM, Cantwell, Bryan bcantw...@firescope.comwrote:
I have successfully set up a replication master/slave scenario with my
MySQL 5.0.51a
Now in the event of a fail over to the slave (an identical appliance), I
want the old master to become
On 8 Jul 2009, at 22:26, Aaron Blew wrote:
The simplest method may be to set them up in a multi-master
configuration,
similar to what's documented here:
http://www.onlamp.com/pub/a/onlamp/2006/04/20/advanced-mysql-replication.html
This way you won't have to worry about switching between two
Hi,
I need to run a longer running insert and test it in the Master Slave
Replication Database Server. And interrupt the Insert query on the Master
and check on slave to ensure that the data is in sync. How can i do it, are
there benchmark tools to do that.
Thanks and Regards
Kaushal
Use the below link to know how to setup replication.
http://dev.mysql.com/doc/refman/5.0/en/replication-howto.html
regards
anandkl
On 4/15/08, Kaushal Shriyan [EMAIL PROTECTED] wrote:
Hi,
I need to run a longer running insert and test it in the Master Slave
Replication Database Server
Hi,
what are the different test cases to test MySQL Master and Slave Replication
Database Server.
Thanks and Regards
Kaushal
In news:[EMAIL PROTECTED],
Rilawich Ango [EMAIL PROTECTED] wrote:
I found the the position in show master status also keep as 98 but I
am sure the replication from S2 to S1 works. It seems that S2 master
hasn't started yet.
If by that you mean that you want the changes made on S1 to be
Hi,
I tried to set a replication as below.
S1(master) --- S2 (slave), (master) -- S3 (slave)
I have set S1 and S2 (slave) without problem. However, there is a
problem in S2 as a master.
I found the the position in show master status also keep as 98 but I
am sure the replication from S2 to S1
Kishore Jalleda schrieb:
Hi you may be having issues with the byte order on the opetron's and the
P4's , this was asked earlier in the list, and here's what Jimmy from Mysql
had to say
Kishore,
Thanks for the suggestion, but all x86 have the same byte order... and
as I wrote its
Could you post the error log entries from the slave and the binlog where the
slave hangs , also just to make sure d2 and d3 replicate well without any
problems from d1 right ? also as per your message d4 and d5 would work well
if no replication is enabled at all so essentially its only the
A neverending story.
I thought it worked (without having an idea what has been the problem),
but it broke down again after a few hours.
My current set up is:
-A p4 production server (Server1) running debian linux, 2.4 kernel,
mysql 4.1.13-standard-log. This server is replicating to several
Hi you may be having issues with the byte order on the opetron's and the
P4's , this was asked earlier in the list, and here's what Jimmy from Mysql
had to say
All machines used in the cluster must have the same architecture; that is,
all machines hosting nodes must be either
I thought I found the reason for my problems with the change in
join-behaviour in mysql 5, but Iwas wrong :( there is more trouble :(
my replications hangs with simple queries like insert into table
(a,b,c) values (1,2,3) on a myisam-table.
It just hangs forever with no cpu-load on the slave.
I've been trying to get my new mysql-5.0.18-servers running as slaves of our
production systems to check if all our applications work fine with mysql 5 and
to do some tests and tuning on the new servers.
The old servers are all P4s, 3GB RAM running debian-linux, 2.4-kernel and
official mysql
Anyone know what to do when SHOW SLAVE STATUS says:
Query caused different errors on master and slave.
Master: MySQL 4.1.9-Debian_2-log
Slave: MySQL 4.1.5-gamma-log
Thanks,
Jacob
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http
.
The question for the list is ... can I use the latest version of mysql on the slave
server so when we upgrade the master
in a few weeks / month the master and slave will be at the same version ? Or does the
slave have to be version 3.23
build 50 ?
Thanks
Michael
--
MySQL General Mailing List
system.
The question for the list is ... can I use the latest version of mysql on the slave
server so when we upgrade the master
in a few weeks / month the master and slave will be at the same version ? Or does the
slave have to be version 3.23
build 50 ?
4.0 slave can replicate 3.23 master
Hello colleagues,
I want to set up a replication schema on MySQL (ISAM tables).
I then have to align the databases before starting the replication.
I would like to NOT stop the database to do the alignment because
the application needs a lot of time to startup (1 hour) and I may have
to start
Hello,
I have basic replication working between a master and slave.
I'm attempting to clarify what happens during a master failure, master
reintegration scenario using heartbeat- and mysql-3.23.52-27.
Clients connect to a movable IP managed by heartbeat.
M=master, S=slave
# my.cnf
I am using 1 master (4.0.13 named PISSARRO ) and 3 slaves (4.0.15); of
course the my.ini are different in the master and slaves.
Today for an error (I thinked to be on my slave) I executed in sequence
these commands:
change master to
Hi list,
I have a question about replication in MySQL.
I have mysql 4.0.12 (master and slave) on windows 2000.
Can I make master and slave on the same computer?
If I have the master on disk c, and the slave on disk d:
1) When do I put the my.ini file of the slave?
2) How can I stop and start
.
---Original Message-
--From: Vico Timmermans [mailto:[EMAIL PROTECTED]
--Sent: Tuesday, May 27, 2003 8:51 AM
--To: [EMAIL PROTECTED]
--Subject: replication - master and slave on the same computer
--
--
--Hi list,
--I have a question about replication in MySQL.
--I have mysql 4.0.12 (master
At 17:51 27/5/2003 +0200, Vico Timmermans wrote:
Hi,
Hi list,
I have a question about replication in MySQL.
I have mysql 4.0.12 (master and slave) on windows 2000.
Can I make master and slave on the same computer?
Yes.
Assuming that you want the master on drive C and the slave on
drive D
I have set up replication and have it working properly for the most part.
If I update the master the slave follows suit. But my slave is a laptop,
that I use for testing but would like that data to stay up to date withthe
master. Overnight if 'live changes take place on the Master, while
At 11:48 -0500 3/11/03, Daniel Negron/KBE wrote:
I have set up replication and have it working properly for the most part.
If I update the master the slave follows suit. But my slave is a laptop,
that I use for testing but would like that data to stay up to date withthe
master. Overnight
the master the slave follows suit. But my slave is a laptop,
that I use for testing but would like that data to stay up to date withthe
master. Overnight if 'live changes take place on the Master, while the
slave is not connected,
How to I sync up the slave ? (without dumping the db or creating a
snapshot
It is automatic.
Next time you connect your laptop to the network,
and start mysqld on your laptop, it will catch up to the master
provided the bin logs are still on the master.
The reason i am asking is because it is not updating a couple of records.
But if I create a new db with some contents
Hello.
I'm build a system aka of Shopping mall.(I think most of queies will be SELECT)
For performance, MySQL will run on replication.
I need TRANSACTIONs to manages orders and payment.
So, Master's Table type is InnoDB.
But I think that InnoDB is slower than MyISAM.
(InnoDB's row level locking
PROTECTED]
cc:(bcc: Murali P/Satyam)
Subject: Different Table type between MASTER and SLAVE
Hello.
I'm build a system aka of Shopping mall.(I think most of queies will be SELECT)
For performance, MySQL will run on replication.
I need TRANSACTIONs to manages orders and payment.
So, Master's
PROTECTED]
cc:(bcc: Murali P/Satyam)
Subject: Different Table type between MASTER and SLAVE
Hello.
I'm build a system aka of Shopping mall.(I think most of queies will be SELECT)
For performance, MySQL will run on replication.
I need TRANSACTIONs to manages orders and payment.
So, Master's
MySQL Bothway Replication - Fail Back - Hold Master while Slave is
Synchronizing.
I have the following question:
Is it possible to have a slave on machine M1 synchronizing with a master
on another machine M2 while the master on the first machine M1 does not
accept requests yet (i.e
Hi there,
I was looking for the master and client source code but I was unable to
find, I found the rpm but not source in tar format.
I ma tiring to configure 2 linux server one master and one slave, can you
tell me what's the best way to accomplish this and what settings I have to
change.
any
Description:
While setting up a mutual master-slave/slave-master MySQL application for
High-Availability, redundancy, and load-balancing, the autoincrement functionality of
disparate servers seem to be detached from replication functionality. It's likely the
replication code can be improved
47 matches
Mail list logo
