Re: how to determine right value for max_allowed_packet?
I think I've foind the culprit: a problem (logical, not physical) had been discovered with a couple of tables which were fixed by truncating them in the production replication master and reloading them from a mysqldump of the corrected tables from the qc/dev database. the dump was done w/the -e (which makes sense) flag hence REALLY BIG individual insert statements even though the table itself wasn't that big nor were any individual rows. does this sound plausible? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: how to determine right value for max_allowed_packet?
Hello. Maybe. Use --skip-extended-insert in this case. Sid Lane [EMAIL PROTECTED] wrote: I think I've foind the culprit: a problem (logical, not physical) had been discovered with a couple of tables which were fixed by truncating them in the production replication master and reloading them from a mysqldump of the corrected tables from the qc/dev database. the dump was done w/the -e (which makes sense) flag hence REALLY BIG individual insert statements even though the table itself wasn't that big nor were any individual rows. does this sound plausible? -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: how to determine right value for max_allowed_packet?
Hello. Are you replicating BLOB or TEXT fields? I think the maximum packet size is correlated with the size of data which is stored in that fields. Sid Lane [EMAIL PROTECTED] wrote: all, I just finshed hosing down a minor (that could have been FAR worse) fire where replication failed with an: Error reading packet from server: Packet too large - increase max_allowed_packet on this server in my error log. I bumped it up from 1M to 4M, restarted mysql (as well as dependant web servers) and replication went back on its merry way and all appears to be well again. my ? is: how do I know how to size this parameter? master slave had been set to the same value (1M). we replicate a fair amount of data (~1GB of binlog/2hr) and have not had any replication errors in the several months since we implimented it so this is a little surprising. FWIW, we're running 4.0.18 on SuSE 9.1. before anyone says it: yes, we're planning on upgrading to 4.1.x but I have to finish an Oracle 10 upgrade 1st. any help would be greatly appreciated... thanks! -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: how to determine right value for max_allowed_packet?
Hello. I've never heard that big values of max_allowed_packed had produced problems. So usually putting it to big enough values shouldn't break anything in most cases. Please, next time send a copy of your message to the list, more experienced users can give a good advice. we are replicating some text columns (though they are a comparitievly small % of our DML volume). that thought had crossed my mind (Oracle used to blame the ORA-00600s AQ kept coughing up on CLOBs). I guess it's certainly possible we had a high water text value come through yesterday. so does the max_allowed_packet need to be big enough to accomodate a row, a DML statement or a transaction (they're in innodb tables)? -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
how to determine right value for max_allowed_packet?
all, I just finshed hosing down a minor (that could have been FAR worse) fire where replication failed with an: Error reading packet from server: Packet too large - increase max_allowed_packet on this server in my error log. I bumped it up from 1M to 4M, restarted mysql (as well as dependant web servers) and replication went back on its merry way and all appears to be well again. my ? is: how do I know how to size this parameter? master slave had been set to the same value (1M). we replicate a fair amount of data (~1GB of binlog/2hr) and have not had any replication errors in the several months since we implimented it so this is a little surprising. FWIW, we're running 4.0.18 on SuSE 9.1. before anyone says it: yes, we're planning on upgrading to 4.1.x but I have to finish an Oracle 10 upgrade 1st. any help would be greatly appreciated... thanks! -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
