Bug #91185 Replication error from master to slave
Submitted: 8 Jun 2018 11:16 Modified: 11 Jul 2018 13:17
Reporter: soma prashanth Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Cluster: Replication Severity:S3 (Non-critical)
Version:5.6.40 OS:Red Hat (MySQL Community Server (GPL))
Assigned to: MySQL Verification Team CPU Architecture:x86

[8 Jun 2018 11:16] soma prashanth
Description:
we see the sql replication failed with the error

mysql> SHOW SLAVE STATUS\G;
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: x.x.x.x
                  Master_User: rep
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: mysql_binary_log.002533
          Read_Master_Log_Pos: 82650265
               Relay_Log_File: mysqld-relay-bin.000002
                Relay_Log_Pos: 3551413
        Relay_Master_Log_File: mysql_binary_log.002524
             Slave_IO_Running: Yes
            Slave_SQL_Running: No
              Replicate_Do_DB:
          Replicate_Ignore_DB:
           Replicate_Do_Table:
       Replicate_Ignore_Table:
      Replicate_Wild_Do_Table:
  Replicate_Wild_Ignore_Table:
                   Last_Errno: 1677
                   Last_Error: Column 0 of table 'navms.NAV_METRICETLSTATUS' cannot be converted from type 'varchar(300)' to type 'varchar(100)'
                 Skip_Counter: 0
          Exec_Master_Log_Pos: 10987097
              Relay_Log_Space: 1021238728
              Until_Condition: None
               Until_Log_File:
                Until_Log_Pos: 0
           Master_SSL_Allowed: No
           Master_SSL_CA_File:
           Master_SSL_CA_Path:
              Master_SSL_Cert:
            Master_SSL_Cipher:
               Master_SSL_Key:
        Seconds_Behind_Master: NULL
Master_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 0
                Last_IO_Error:
               Last_SQL_Errno: 1677
               Last_SQL_Error: Column 0 of table 'navms.NAV_METRICETLSTATUS' cannot be converted from type 'varchar(300)' to type 'varchar(100)'
  Replicate_Ignore_Server_Ids:
             Master_Server_Id: 1
                  Master_UUID: 6f70f11c-083b-11e5-8335-000f5328e04c
             Master_Info_File: mysql.slave_master_info
                    SQL_Delay: 0
          SQL_Remaining_Delay: NULL
      Slave_SQL_Running_State:
           Master_Retry_Count: 86400
                  Master_Bind:
      Last_IO_Error_Timestamp:
     Last_SQL_Error_Timestamp: 180607 16:08:22
               Master_SSL_Crl:
           Master_SSL_Crlpath:
           Retrieved_Gtid_Set:
            Executed_Gtid_Set:
                Auto_Position: 0
1 row in set (0.00 sec)

=======================

there is no change in the table definition on both the master and slave 

mysql> describe navms.NAV_METRICETLSTATUS;
+----------------+--------------+------+-----+-------------------+-----------------------------+
| Field          | Type         | Null | Key | Default           | Extra                       |
+----------------+--------------+------+-----+-------------------+-----------------------------+
| METRICIDENTITY | varchar(100) | NO   | PRI | NULL              |                             |
| DATEOFLASTLOAD | timestamp    | NO   |     | CURRENT_TIMESTAMP | on update CURRENT_TIMESTAMP |
| ETLSTATE       | text         | YES  |     | NULL              |                             |
+----------------+--------------+------+-----+-------------------+-----------------------------+
3 rows in set (0.00 sec)

How to repeat:
Iam looking for afix
[11 Jun 2018 13:17] MySQL Verification Team
Hi,
I'm sorry but I don't see the issue? 
For start, this does not look in any way related to MySQL Cluster?
Can you please explain what issue you have and on what configuration?

thanks
Bogdan
[11 Jun 2018 13:18] MySQL Verification Team
also please provide full show create table on both master and server, and check default character sets as that looks like latin1 vs utf8
[12 Jul 2018 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".