mysql - replication slave has less space -


i need setup replication

so took backup master , imported slave , slave has 20 gb free space, @ time while restoring backup master got 5+ gb of data

after enabled replication

now problem while data relay log written slave many new relay logs generated , left no space on slave....

the relay-log-purge enabled writing process relay log database slow...

you may have performance benefits switching binlog format 'row'. in mixed format mysql writing binlog statement based (the slave has reparse , plan strategy again) , switches row format in cases (http://dev.mysql.com/doc/refman/5.1/en/binary-log-mixed.html).

it can done on fly:

set global binlog_format = 'row'; 

with row based replication can offload slaves makes them easier keep master. downside of may have larger log files "got 5+ gb of data" assume inserts there no difference.

best try , see how behaves.

other option until replication catches change innodb_flush_log_at_trx_commit 2 on slave. temporary.

set global innodb_flush_log_at_trx_commit = 2; 

Comments

Popular posts from this blog

monitor web browser programmatically in Android? -

Shrink a YouTube video to responsive width -

wpf - PdfWriter.GetInstance throws System.NullReferenceException -