tag:blogger.com,1999:blog-18337119.post116620210177665982..comments2024-01-22T07:09:30.574-05:00Comments on MySQL Consulting and NoSQL Consulting: MySQL DBA: MySQL: Replication stopped: Lock wait timeout exceededUnknownnoreply@blogger.comBlogger3125tag:blogger.com,1999:blog-18337119.post-28512122614187445862007-05-17T09:47:00.000-04:002007-05-17T09:47:00.000-04:00where I have to mention this lock time out propert...where I have to mention this lock time out property i am using java I didn't found any option to set this.is this should be done on mysql sideRoseshttps://www.blogger.com/profile/09542636820900023946noreply@blogger.comtag:blogger.com,1999:blog-18337119.post-1166298447227347622006-12-16T14:47:00.000-05:002006-12-16T14:47:00.000-05:00Hi Frank!slave_transaction_retries (default value ...Hi Frank!<BR/><BR/>slave_transaction_retries (default value 10) was added in 4.1.11 to help fix this issue. The SQL thread should retry the transaction 10 times before giving up. If this is set to the default value The SQL retried 10 times before giving up. This means that a lock was held for ~500 seconds. Try to find what is causing this lock and fix it. 500 seconds is a long time to hold on to a lock.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-18337119.post-1166232487073362912006-12-15T20:28:00.000-05:002006-12-15T20:28:00.000-05:00This has happened to me on 4.0.26. It was not a pr...This has happened to me on 4.0.26. It was not a problem in 4.0.20. My problem occurs because other sessions were doing 'insert ... select foo' where the SQL replication thread was trying to update foo. In some versions of MySQL, InnoDB will get S locks on foo. This is required on the master to guarantee consistency of the transaction between a master on slaves. But the lock was also obtained when the binlog was disabled. See ha_innobase::store_lock for details.Anonymousnoreply@blogger.com