Bug #64794 | slave-skip-errors does not work when using ROW based replication REDUX | ||
---|---|---|---|
Submitted: | 28 Mar 2012 23:00 | Modified: | 16 Nov 2017 10:09 |
Reporter: | Matthew Montgomery | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Row Based Replication ( RBR ) | Severity: | S3 (Non-critical) |
Version: | 5.1.56 | OS: | Any |
Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
[28 Mar 2012 23:00]
Matthew Montgomery
[30 Mar 2012 20:31]
Kolbe Kegel
It appears that error #1677 (Column %d of table '%s.%s' cannot be converted from type '%s' to type '%s') from a row-based event also stops replication even with slave_skip_errors=all set.
[7 Aug 2013 17:02]
Andrew McGill
This error persists in version 5.6.13, where I am battling stacks of 1677 errors saying "(fieldname) cannot be converted from type 'timestamp' to type 'timestamp'"
[19 Feb 2014 16:14]
Carlos Vazquez
This is also occurring to me in 5.6.15 Community edition Linux RPM on CentOS 6.4. It happens with both slave_skip_errors = 1677 and slave_skip_errors = all
[13 Jan 2015 15:12]
Stefan Hinz
Closed by mistake, sorry. Reopened. -Stefan
[15 Feb 2016 21:35]
Rick Dale
Still having this issue in 5.6.28-enterprise. Any updates?
[16 Nov 2017 10:09]
Erlend Dahl
Fixed in 5.6.32 and up under the heading of Bug#17653275.