RE: mysqldump with single-transaction with high-concurrency DB

easy enough to reproduce, but unfortunately I cannot as this is my production DB. -Original Message- From: Devananda [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 11, 2006 10:59 AM To: Mark Steele Cc: mysql@lists.mysql.com Subject: Re: mysqldump with single-transaction with high-concurrency

RE: mysqldump with single-transaction with high-concurrency DB

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 defaul

RE: mysqldump with single-transaction with high-concurrency DB

implied in the documentation). If this isn't the case in high-concurrency situations, anyone have another method to get a consistent snapshot? Cheers, Mark -Original Message- From: Dan Buettner [mailto:[EMAIL PROTECTED] Sent: Monday, July 10, 2006 3:21 PM To: Mark Steele Cc: mysql@lists.m

mysqldump with single-transaction with high-concurrency DB

gle-transaction as taking a short global lock, which is the root cause of the deadlock I saw I believe. When the server was deadlocked, all the connections were 'waiting on table', and the backup process was apparently stuck on 'flushing tables'. Cheers, Mark Steele

RE: MySQL support for AMD64

). Cheers, Mark Steele Implementation Director CDT Inc. -Original Message- From: Lynn Bender [mailto:[EMAIL PROTECTED] Sent: November 30, 2004 2:23 PM To: [EMAIL PROTECTED] Subject: MySQL support for AMD64 I just received a box with the following specs: Dual AMD64 8G ram Two 3ware 2.4 ter

RE: Fast method needed to determine if a table is corrupt

NVRAM to store the database). Other than that, there's no quick way to check for corruption that I know of. Cheers, Mark Steele Implementation Director CDT Inc. -Original Message- From: Dan Nelson [mailto:[EMAIL PROTECTED] Sent: November 8, 2004 12:43 PM To: Tim Murtaugh C

memory utilization

efficiently? Also most of the tables (almost all of them) will be using the InnoDB storage engine, any pointers on what configuration settings we should use? (for example on a 16 gb RAM server) Anyone have experience with this kind of setup? Regards, Mark Steele Implementation Director CDT Inc. Tel

RE: Innodb assertion failure after binary backup-restore

://www.innodb.com) works very well even on large databases (currently we backup over 40 gigs/day). Cheers, Mark Steele Implementation Director CDT Inc. -Original Message- From: Sp.Raja [mailto:[EMAIL PROTECTED] Sent: July 27, 2004 10:51 AM To: Heikki Tuuri; [EMAIL PROTECTED] Subject: Re

RE: Script to purge

atios, so it's worth just archiving them. Here's the script (see the web site for explanations) #!/usr/bin/perl ## Binary log backup utility ## Author: Mark Steele <[EMAIL PROTECTED]> ## Bug: This script will fail when you hit binlog #999 and roll over to 1 ## I'm t

long queries with InnoDB...

ables? Regards, Mark Steele Implementation Director CDT inc. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

RE: slave hotbackup question

other Slave than having to take snapshots of the master, as this is disruptive in a mixed InnoDB/MyISAM environment (We are doing somewhere in the vicinity of 500 queries/sec in peak times). Regards, Mark Steele Implementation Director CDT Inc. [EMAIL PROTECTED] -Original Message- From: H

slave hotbackup question

the innodb backup,ibbackup waits for a backup to be taken of the MyISAM tables and table definitions (lock tables with read lock, copy the *.FRM, *.MYI, *.MYD files, unlock). Once the MyISAM tables and table definitions are backed up, ibbackup resumes and theoretically I _should_ have a consistent backup of the whole database server once ibbackup is finished. (although I truncate the MyISAM index files, but they can be reconstructed with myisamchk -r) My question is, suppose I would like to use one of these backups to create a new slave server, what additional information would I need to include in the backup to be able to start up a new slave properly? (relay logs/info files, etc...) Ideally, I would like these snapshots to be taken off the running server while it is in use, is there any way to do this? Regards, Mark Steele Implementation Director CDT Inc. [EMAIL PROTECTED] PS: the perl code is sloppy and needs more error checking,etc... use at your own risk. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]