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
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
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
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
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
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
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
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
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
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
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,
11 matches
Mail list logo
