mysql3308错误_mysql从库出错

今天收到邮件，mysql3308,同步出错，日志如下：

修改配置文件  my.cnf ,添加：

innodb_buffer_pool_size = 16M

重启mysql,解决，

---------

参考：

在操作mysql数据库表时出现以下错误。

网上google搜索相关问题，发现一位外国牛人这么解释：

If you're running an operation on a large number of rows within a table that uses the InnoDB storage engine, you might see this error:

ERROR 1206 (HY000): The total number of locks exceeds the lock table size

MySQL is trying to tell you that it doesn't have enough room to store all of the row locks that it would need to execute your query. The only way to fix it for sure is to adjust innodb_buffer_pool_size and restart MySQL. By default, this is set to only 8MB, which is too small for anyone who is using InnoDB to do anything.

If you need a temporary workaround, reduce the amount of rows you're manipulating in one query. For example, if you need to delete a million rows from a table, try to delete the records in chunks of 50,000 or 100,000 rows. If you're inserting many rows, try to insert portions of the data at a single time.

原来是InnoDB表执行大批量数据的更新，插入，删除操作时会出现这个问题，需要调整InnoDB全局的innodb_buffer_pool_size的值来解决这个问题，并且重启mysql服务。

查看当前数据库存储引擎，在创建时使用ENGINE=InnoDB类型。

默认的innodb_buffer_pool_size=8M

修改 innodb_buffer_pool_size的值：

点击(此处)折叠或打开

innodb_buffer_pool_size=64M

再一次重启mysql服务器，执行表操作，成功执行完毕。

----------------------

2015-12-31

今天mysql从库报错：

Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave.

1，检查主库的mysql-bin  log日志，出现以下错误：

ERROR: Error in Log_event::read_log_event(): 'Found invalid event in binary log', data_len: 116, event_type: 19

2，跟开发联系了一下，他说是自己手动执行了一个sql，是分成两行写的；