Bug #106388 Using SPATIAL KEY cause replication error 1032
Submitted: 7 Feb 2022 1:07 Modified: 7 Feb 2022 7:56
Reporter: nanzhou lin Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Replication Severity:S2 (Serious)
Version:5.7, 5.7.37 OS:Any
Assigned to: CPU Architecture:Any

[7 Feb 2022 1:07] nanzhou lin
Description:
when update data is will report error 1032. 
mysql> show slave status\G
*************************** 1. row ***************************               
Slave_IO_State:                  
Master_Host: 192.168.57.111                  
Master_User: test                  
Master_Port: 3306                
Connect_Retry: 60              
Master_Log_File: mysql-bin.219173          
Read_Master_Log_Pos: 80755300               
Relay_Log_File: rds_mysql-relay-bin.000002                
Relay_Log_Pos: 33048        
Relay_Master_Log_File: mysql-bin.219172             
Slave_IO_Running: No            
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: 1032                   
Last_Error: Coordinator stopped because there were error(s) in the worker(s). The most recent failure being: Worker 2 failed executing transaction  
'bc973610-280f-11eb-b3b9-fa163ee7ea64:69444673' at master log mysql-bin.219172, end_log_pos 15735717. See error log and/or performance_schema.                   
replication_applier_status_by_worker table for more details about this failure or others, if any.                 
Skip_Counter: 0          
Exec_Master_Log_Pos: 4128545              
Relay_Log_Space: 92708588              
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: 1032               
Last_SQL_Error: Coordinator stopped because there were error(s) in the worker(s). The most recent failure being: Worker 2 failed executing transaction 'bc973610-280f-11eb-b3b9-fa163ee7ea64:69444673'
 at master log mysql-bin.219172,                end_log_pos 15735717. See error log and/or performance_schema.replicati on_applier_status_by_worker table for more details about this failure or others, if any.  
Replicate_Ignore_Server_Ids:              
Master_Server_Id: 245818808                  
Master_UUID: bc973610-280f-11eb-b3b9-fa163ee7ea64             
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: 220104 05:02:30               
Master_SSL_Crl:            
Master_SSL_Crlpath:            
Retrieved_Gtid_Set: bc973610-280f-11eb-b3b9-fa163ee7ea64:69444198-69446259            
Executed_Gtid_Set: bc973610-280f-11eb-b3b9-fa163ee7ea64:1-69444672                
Auto_Position: 1        
Replicate_Rewrite_DB:                  
Channel_Name:            
Master_TLS_Version: 1 row in set (0.00 sec)

How to repeat:

CREATE TABLE `t2` ( `id` int(11) NOT NULL ', `p` point NOT NULL , `ttext` varchar(50) DEFAULT NULL , SPATIAL KEY p(p)) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4
INSERT INTO `t2` (id, p,ttext ) VALUES (1, ST_PointFromText('POINT(1 1)') ,'first point');
INSERT INTO `t2` (id, p,ttext ) VALUES (2, ST_PointFromText  ( 'POINT(2 2)' ),'second point');
INSERT INTO `t2` (id, p,ttext ) VALUES (3, ST_PointFromText  ( 'POINT(4 3)' ),'third point');
update `t2` set p=ST_PointFromText('POINT(5 5)') where id =1;
[7 Feb 2022 7:56] MySQL Verification Team
Hello nanzhou nanzhou,

Thank you for the report and feedback.
Verified as described with 5.7.37 build.

regards,
Umesh
[7 Feb 2022 9:12] MySQL Verification Team
5.7.37, 8.0.28 test results

Attachment: 106388_8.0.28_5.7.37 (application/octet-stream, text), 18.87 KiB.