innodb - Abnormally high MySQL writes and larger than normal Binary Log files. How can I determine what caused this? -
we have mysql master database replicates mysql slave. experiencing issues mysql showing high number of writes (but not increased number of queries being ran) short period of time (a few hours). trying investigate cause.
normally our binary logs 1 gb in file size during period experiencing these issues, log files jumped 8.5 gb.
when run mysqlbinlog --short-form binarylog.0000
on 1 of 8.5 gb binary log returns 196 kb of queries , data. when run mysqlbinlog --short-form
on normal binary log (1 gb) returns around 8,500 kb worth of queries , database activity. doesn't make sense because has 7 gb more of data yet returns less 1 gb binary log file.
i see lots of these statements sequential timestamps, i'm not sure if that's related problem because they're in both normal period when experienced these issues.
set timestamp=1391452372/*!*/;commit/*!*/; set timestamp=1391452372/*!*/;begin/*!*/;commit/*!*/; set timestamp=1391452372/*!*/;begin/*!*/;commit/*!*/; set timestamp=1391452372/*!*/;begin/*!*/;commit/*!*/;
how can determine caused binary logs balloon in size caused high writes, so took server offline @ points, ddos attack would?
how mysqlbinlog
return less data, though binary log file had 7 gb more? can identify difference between normal period binary logs 1 gb period had issues 8 gb binary log? thank can provide.
bill
i guess log contains form of load data [local] infile
commands , data files associated them. these commands not generate sql output data written temporary file mysqlbinlog
during processing. can check if output contains such load data
commands?
Comments
Post a Comment