Re: mysqldump --single-transaction causes database to become unusable

2007-03-08 Thread Filip Krejci
Hi, I suppose this is really I/O problem. What says vmstat during backup? I see many fsyncs, so you have probably innodb_flush_log_at_trx_commit=1 Try to set innodb_flush_log_at_trx_commit=2 If it solve your problem and you need innodb_flush_log_at_trx_commit=1, install battery backed write

Re: mysqldump --single-transaction causes database to become unusable

2007-03-08 Thread Ian P. Christian
Filip Krejci wrote: > Hi, > > I suppose this is really I/O problem. > You're right, it looks like it was just an I/O problem - your suggestion was spot on. I've now managed to dump my master data, and can get my slave back online! Thanks a lot for your suggestion, -- Ian P. Christian ~ http://p

Re: mysqldump --single-transaction causes database to become unusable

2007-03-08 Thread Ian P. Christian
Filip Krejci wrote: > Hi, > > you are right, option --single-transaction does not accquire any lock on > your innodb tables. Backup is fully on-line due to mvcc. > > You should look for another reason of this behavior. > > 1/ What says 'show full processlist' when backup is running > 2/ What says

Re: mysqldump --single-transaction causes database to become unusable

2007-03-08 Thread Maciej Dobrzanski
In news:[EMAIL PROTECTED], "Ian P. Christian" <[EMAIL PROTECTED]> wrote: > This database I'm dumping has something like 17 million rows, all but > 1 table (which uses FULLTEXT, and only has 3-4k rows) run innodb. > There is only one table of any real size, and this table has all but > about 100k o

Re: mysqldump --single-transaction causes database to become unusable

2007-03-07 Thread Filip Krejci
I have few information, but i suppose that you are on performance border of your db server. So you haven't reserve for doing backup. Send some few rows of command vmstat 1, before backup process and through backup process. How are these numbers: - queries per second ? - updates / selects rate

Re: mysqldump --single-transaction causes database to become unusable

2007-03-07 Thread Marcus Bointon
On 7 Mar 2007, at 09:30, Ian P. Christian wrote: --single-transaction Creates a consistent snapshot by dumping all tables in a single transaction. Works ONLY for tables stored in storage engines which support multiversioning (currently only InnoDB does); the dump is NOT guaranteed to be consist

Re: mysqldump --single-transaction causes database to become unusable

2007-03-07 Thread Ian P. Christian
Filip Krejci wrote: Hi, you are right, option --single-transaction does not accquire any lock on your innodb tables. Backup is fully on-line due to mvcc. You should look for another reason of this behavior. 1/ What says 'show full processlist' when backup is running It shows mostly inserts

Re: mysqldump --single-transaction causes database to become unusable

2007-03-07 Thread Filip Krejci
Hi, you are right, option --single-transaction does not accquire any lock on your innodb tables. Backup is fully on-line due to mvcc. You should look for another reason of this behavior. 1/ What says 'show full processlist' when backup is running 2/ What says 'show engine innodb\G' when backu

Re: mysqldump --single-transaction causes database to become unusable

2007-03-07 Thread Ian P. Christian
Marcus Bointon wrote: Hi Marcus :) > On 7 Mar 2007, at 08:44, Ian P. Christian wrote: > > --single-transaction doesn't _do_ the dump as a transaction, it simply > wraps the dump in begin/commit statements so it's atomic when restoring. > > If the dump is to preserve relational integrity then it

Re: mysqldump --single-transaction causes database to become unusable

2007-03-07 Thread Praj
Hi , --single-transaction will execute the same nature of mysqldump command with begin and end transaction. How ever the table is locked for the backup your site may be slow. -- Praj Ian P. Christian wrote: Recently my one and only slave went down, and stupidly I don't have a dump suitable

Re: mysqldump --single-transaction causes database to become unusable

2007-03-07 Thread Marcus Bointon
On 7 Mar 2007, at 08:44, Ian P. Christian wrote: mysqldump --master-data --single-transaction database > dump.sql This database I'm dumping has something like 17 million rows, all but 1 table (which uses FULLTEXT, and only has 3-4k rows) run innodb. There is only one table of any real size,

mysqldump --single-transaction causes database to become unusable

2007-03-07 Thread Ian P. Christian
Recently my one and only slave went down, and stupidly I don't have a dump suitable for reseeding (is that's the right term...) the slave, so need to make a snapshot of the master database again. This time I'll make sure I keep this datafile for future restores should I need to - you live and l

Re: dose mysqldump --single-transaction lock table?

2006-09-13 Thread Chris
Leo wrote: > Hi,all.I want to use mysqldump to backup a innodb table,and add the option > --single-transaction,dose it lock all the table?thanks. It has to so it can give you one transaction and make sure nothing else gets entered after it starts and before it finishes. -- MySQL General Mailing

dose mysqldump --single-transaction lock table?

2006-09-13 Thread Leo
Hi,all.I want to use mysqldump to backup a innodb table,and add the option --single-transaction,dose it lock all the table?thanks. -- Leo 2006-09-13 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:ht

Re: Question on mysqldump --single-transaction

2006-07-05 Thread Chris
n? Or is it one transaction per database (or even table?)? I could not find an answer to this in the documentation. The easiest way to find out? create database blah; create table blah1(id int); create table blah2(id int); see what mysqldump --single-transaction does and post a comment on the

Question on mysqldump --single-transaction

2006-07-05 Thread Dominik Klein
Hi everyone I'm wondering about the "--single-transaction" option on mysqldump. Documentation says --- This option issues a BEGIN SQL statement before dumping data from the server. ... --- So does this include the entire dump in one transaction? Or is it one transaction per database (or even

Re: mysqldump, --single-transaction and --flush-logs

2005-04-11 Thread Gleb Paharenko
Hello. I think you may use a General Query Log to find out a sequence of queries which mysqldump will perform. > Is there some way to determine the binary log position as of the > single transaction for the dump? --master-data might be helpful. "Bill Easton" <[EMAIL PROTECTE

mysqldump, --single-transaction and --flush-logs

2005-04-11 Thread Bill Easton
If I use the options --single-transaction and --flush-logs with mysqldump and InnoDB tables, does the new log file start at the same time as the transaction? If not, is it known for sure if the log file is switched before the transaction starts or if it is switched after the transaction starts? I

Re: mysqldump --single-transaction

2003-08-18 Thread Jeremy Zawodny
On Mon, Aug 18, 2003 at 04:14:21PM +1000, Chris Nolan wrote: > Hi all! > > Currently, one of my clients has a MySQL+InnoDB database that they use for > storing "stuff". My question is, even though I know it will take more time > and will slow down operations for everyone, will mysqldump with the s

mysqldump --single-transaction

2003-08-17 Thread Chris Nolan
Hi all! Currently, one of my clients has a MySQL+InnoDB database that they use for storing "stuff". My question is, even though I know it will take more time and will slow down operations for everyone, will mysqldump with the single transaction option give a consistant snapshot of InnoDB tables if