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]
