2023-03-29T17:49:04.251874+08:00 102 [Note] [MY-010581] [Repl] Slave SQL thread for channel 'group_replication_recovery' initialized, starting replication in log 'FIRST' at position 0, relay log './hrt-sw-flsc-db-prd-5-vm-02-relay-bin-group_replication_recovery.000001' position: 4 2023-03-29T17:49:04.262870+08:00 103 [ERROR] [MY-010584] [Repl] Slave SQL for channel 'group_replication_recovery': Worker 1 failed executing transaction '48d27cf3-4d1d-5641-7add-d857bdee6d3c:25' at master log binlog.0 CONSTRAINT `qrtz_blob_triggers_ibfk_1` FOREIGN KEY (`SCHED_NAME`, `TRIGGER_NAME`, `TRIGGER_GROUP`) REFERENCES `common`.`qrtz_triggers` (`SCHED_NAME`, `TRIGGER_NAME`, `TRIGGER_GROUP`) ON DELETE RESTRICT ON UPDATE RES ) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci', Error_code: MY-001049 2023-03-29T17:49:04.263359+08:00 102 [ERROR] [MY-010586] [Repl] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'binlog.000002' position 9518 |
合作电话:010-64087828
社区邮箱:greatsql@greatdb.com