Hi,
Inserting the value* innodb_flush_log_at_trx_commit=2* in my.cnf
did the trick (innodb_flush_log_at_trx_commit=0 works fine two), but the
default value (innodb_flush_log_at_trx_commit=1), seems to be doing
something wrong.
One full backup (7 GB) has decreased the backup time from 4h (45
spo
Hi Cejka,
The server runs smooth :
top - 14:11:06 up 20:18, 2 users, load average: 0.00, 0.01, 0.24
Tasks: 154 total, 1 running, 153 sleeping, 0 stopped, 0 zombie
Cpu0 : 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si,
0.0%st
Cpu1 : 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.
Iban Cabrillo wrote (2013/11/27):
> Data spooling: 0 active jobs, 0 bytes; 1 total jobs, 1,845,487,814 max
> bytes/job.
> Attr spooling: 1 active jobs, 18,289,433 bytes; 0 total jobs, 18,289,433
> max bytes.
>
> Data spooling about 10 minutes, Attr Spooling more than 30 minutes and
> growing
Hi,
I have seen lots of threads we this subject but no one with a solution.
Despooling Attributes takes a very very long time. Seem no to be a
question about tunning mysql.
Data spooling: 0 active jobs, 0 bytes; 1 total jobs, 1,845,487,814 max
bytes/job.
Attr spooling: 1 active jobs, 18,289,43
