-
From: Dan Buettner [mailto:[EMAIL PROTECTED]
Sent: Monday, July 10, 2006 3:21 PM
To: Mark Steele
Cc: mysql@lists.mysql.com
Subject: Re: mysqldump with single-transaction with high-concurrency DB
Sorry Mark - I thought your question was more of a does this seem
right and how do I than a something's
replication setup is via snapshots on the master.
-Original Message-
From: Dan Buettner [mailto:[EMAIL PROTECTED]
Sent: Monday, July 10, 2006 2:42 PM
To: Mark Steele
Cc: mysql@lists.mysql.com
Subject: Re: mysqldump with single-transaction with high-concurrency
DB
Mark, that's
To: Mark Steele
Cc: mysql@lists.mysql.com
Subject: Re: mysqldump with single-transaction with high-concurrency DB
Sorry Mark - I thought your question was more of a does this seem
right and how do I than a something's wrong here post.
I think your problem is coming in with the use of --opt
5.0.22
-Original Message-
From: Dan Buettner [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 11, 2006 9:55 AM
To: Mark Steele
Cc: mysql@lists.mysql.com
Subject: Re: mysqldump with single-transaction with high-concurrency DB
Sorry Mark, appears you're right. --opt is the default now
10, 2006 3:21 PM
To: Mark Steele
Cc: mysql@lists.mysql.com
Subject: Re: mysqldump with single-transaction with high-concurrency
DB
Sorry Mark - I thought your question was more of a does this seem
right and how do I than a something's wrong here post.
I think your problem is coming
Hi folks,
I've recently tried to do a database backup on a database server that
has a fairly high concurrency rate (1000+ queries/sec) and have noticed
that the backup process seemed to deadlock the machine and I had to
resort to extreme measures to get the database back up (killed the
process
Mark, that's the expected behavior of mysqldump with --opt and
--single-transaction; it locks all databases and all tables for the
duration of the dump, ensuring a consistent snapshot.
With a database this size (100 GB), it's an area where throwing
hardware at the problem may be your best bet.
.
-Original Message-
From: Dan Buettner [mailto:[EMAIL PROTECTED]
Sent: Monday, July 10, 2006 2:42 PM
To: Mark Steele
Cc: mysql@lists.mysql.com
Subject: Re: mysqldump with single-transaction with high-concurrency DB
Mark, that's the expected behavior of mysqldump with --opt and
--single
: mysqldump with single-transaction with high-concurrency DB
Sorry Mark - I thought your question was more of a does this seem
right and how do I than a something's wrong here post.
I think your problem is coming in with the use of --opt. The article
you reference, where it says This is an online
