[Maria-docs] MariaDB Binary Log File Corruption
Hello everyone,
I came across this question in the Knowledgebase:
http://kb.askmonty.org/v/binary-log-file-corruption-happens-each-day
The poster was able to solve the problem by increasing the slave max_allowed_packet size from 32M to 256M.
Any thoughts from the list about this? My guess is that this not a MariaDB-specific thing; just a difference between 5.0 and 5.1 (and higher). But I'm asking anyway in case I'm mistaken and/or if a note should be added to the documentation for max_allowed_packet.
Thanks.
Hi Daniel
On Tue, Jan 18, 2011 at 10:29 PM, Daniel Bartholomew dbart@montyprogram.com wrote:
Hello everyone,
I came across this question in the Knowledgebase:
http://kb.askmonty.org/v/binary-log-file-corruption-happens-each-day
The poster was able to solve the problem by increasing the slave max_allowed_packet size from 32M to 256M.
Any thoughts from the list about this?
I remember this is one of the cases covered in the newest Percona white paper: http://www.percona.com/files/white-papers/preventing-mysql-emergencies.pdf
I think the solution was basically what you say above too. I've never personally encountered this.
(It's an excellent white paper btw, one of the best ever I've read.)
henrik
participants (2)
-
Daniel Bartholomew
-
Henrik Ingo