| Bug #19896 | Last_Errno: 4294967295, Error in Write_rows event: (error number 4 billion?) | ||
|---|---|---|---|
| Submitted: | 18 May 2006 1:10 | Modified: | 8 Feb 2007 7:58 |
| Reporter: | Jonathan Miller | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Cluster: Replication | Severity: | S3 (Non-critical) |
| Version: | 5.1.11 | OS: | Linux (Linux 32 Bit OS) |
| Assigned to: | david li | CPU Architecture: | Any |
[1 Sep 2006 15:28]
Calvin Sun
4294967295 = -1 (4-bytes)
[23 Nov 2006 1:44]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/15745 ChangeSet@1.2320, 2006-11-23 09:47:18+08:00, dli@dev3-76.dev.cn.tlan +2 -0 ndb - fixed for BUG#19896 Last_Errno: 4294967295, Error in Write_rows event: (error number 4 billion ?) fixed to use int instead of uint32 type to return last_slave_errno.
[22 Dec 2006 2:01]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/17299 ChangeSet@1.2320, 2006-12-22 09:59:27+08:00, dli@dev3-164.dev.cn.tlan +3 -0 ndb - fixed for BUG#19896 Last_Errno: 4294967295, Error in Write_rows event: (error number 4 billion ?) fixed to use int instead of uint32 type to return last_slave_errno.
[7 Feb 2007 17:00]
Tomas Ulin
pushed to 5.1.16
[8 Feb 2007 7:58]
Jon Stephens
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.
If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at
http://dev.mysql.com/doc/en/installing-source.html
Documented bugfix in 5.1.16 changelog.
Description: I don't think that our error messages have gotten into the 4 billion count yet. One of the data nodes was shut down on the slave by the abirtrator due to missing heart beats. This cause replication to fail and when doing a show slave status, this is what I found: Last_Errno: 4294967295 Last_Error: Error in Write_rows event: when locking tables Error log: 060518 1:54:07 [ERROR] Slave: Error in Write_rows event: error during transaction execution on table cluster.apply_status, Error_code: 4010 060518 1:54:07 [ERROR] Slave: Error in Write_rows event: when locking tables, Error_code: -1 060518 1:54:07 [ERROR] Slave (additional info): Can't lock file (errno: 4009) Error_code: 1015 060518 1:54:07 [Warning] Slave: Got error 4009 'Cluster Failure' from NDB Error_code: 1296 060518 1:54:07 [Warning] Slave: Can't lock file (errno: 4009) Error_code: 1015 060518 1:54:07 [Warning] Slave: Unknown error Error_code: 1105 060518 1:54:07 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'ndb0901binlog.000001' position 317171899 How to repeat: Setup a Master and Slave CLuster and start DBT2 Suggested fix: Error message may actually be a signed negative 4 byte number issue.