What is the cause for the error 1610 This morning, I had the following event:


  200310  9:54:57 [ERROR] Slave SQL: Could not execute Update_rows event on table Call_Center_Infinit.queue_member_table; Corrupted replication event  was detected, Error_code: 1610; Corrupted replication event was detected, Error_code: 1610; handler error No Error!; the event's master log  log TN-TX-DB03-bin.000972, end_log_pos 551613719, Error_code: 1610.


I ran mysqlbinlog --base64-output=DECODE-ROWS -vv  log TN-TX-DB03-bin.000972 and search "end_log_pos 551613719" using vi, I found the following:

#200310  9:54:57 server id 6  end_log_pos 551611999     Query   thread_id=2180761724    exec_time=0     error_code=0
SET TIMESTAMP=1583855697/*!*/;
BEGIN
/*!*/;
# at 551611999
# at 551612137
# at 551612227
# at 551612741
# at 551613719

#200310  9:54:57 server id 6  end_log_pos 551612137     Table_map: `Call_Center_Infinit`.`Agentes` mapped to number 1089
#200310  9:54:57 server id 6  end_log_pos 551612227     Table_map: `Call_Center_Infinit`.`queue_member_table` mapped to number 1140
#200310  9:54:57 server id 6  end_log_pos 551612741     Update_rows: table id 1089
#200310  9:54:57 server id 6  end_log_pos 551613719     Update_rows: table id 1140

### UPDATE `Call_Center_Infinit`.`queue_member_table`
### WHERE
###   @1=189482 /* INT meta=0 nullable=0 is_null=0 */
###   @2=NULL /* INT meta=0 nullable=1 is_null=1 */
###   @3=52984 /* INT meta=0 nullable=1 is_null=0 */
###   @4=53740 /* INT meta=0 nullable=1 is_null=0 */
###   @5='53740' /* VARSTRING(40) meta=40 nullable=1 is_null=0 */
###   @6='52984' /* VARSTRING(128) meta=128 nullable=1 is_null=0 */
###   @7='Agent/53740' /* VARSTRING(128) meta=128 nullable=1 is_null=0 */
###   @8=NULL /* VARSTRING(128) meta=0 nullable=1 is_null=1 */
###   @9=0 /* INT meta=0 nullable=1 is_null=0 */
###   @10='' /* VARSTRING(80) meta=80 nullable=0 is_null=0 */
### SET
###   @1=189482 /* INT meta=0 nullable=0 is_null=0 */
###   @2=NULL /* INT meta=0 nullable=1 is_null=1 */
###   @3=52984 /* INT meta=0 nullable=1 is_null=0 */
###   @4=53740 /* INT meta=0 nullable=1 is_null=0 */
###   @5='53740' /* VARSTRING(40) meta=40 nullable=1 is_null=0 */
###   @6='52984' /* VARSTRING(128) meta=128 nullable=1 is_null=0 */
###   @7='Agent/53740' /* VARSTRING(128) meta=128 nullable=1 is_null=0 */
###   @8=NULL /* VARSTRING(128) meta=0 nullable=1 is_null=1 */
###   @9=1 /* INT meta=0 nullable=1 is_null=0 */
###   @10='' /* VARSTRING(80) meta=80 nullable=0 is_null=0 */


according to me, from here is stopped replica
How was the "rotation" done?  Normally you should never need to "rotate the binlog".  1.1G is normal when max_binlog_size is 1G; it overshoots, then automatically rotates.

You could change that setting to 100M with no harm.  That will cause for frequent rotation, and each file will be about 100MB.