[MDEV-20348] DROP TABLE IF EXISTS killed on master but was replicated. - Jira

Following steps were performed by a process:

DROP TABLE IF EXISTS `tmp_1e` /* generated by server */

CREATE TABLE tmp_1 LIKE perm_1 /* ainternal305, gs:361F952CDB0FF3C076C373243996193F, tx:ddb58f2cdb873bc076c3732439961936 */

DELETE IGNORE FROM tmp_1 WHERE tmp_1.sys_id = OLD.sys_id;

REPLACE INTO tmp_1(`u_configuration_item`,`sys_id`) VALUES (NEW.`u_configuration_item`,NEW.`sys_id`);

REPLACE INTO tmp_1 (`u_configuration_item`,`sys_id`) VALUES (NEW.`u_configuration11111_item`,NEW.`sys_id`);

DROP TABLE IF EXISTS `z_tmp_1` /* generated by server */

RENAME TABLE perm_1 TO z_tmp_1, tmp_1 TO perm_1 /* a305, gs:361F952CDB0FF3C076C373243996193F, tx:ddb58f2cdb873bc076c3732439961936 */

DROP TABLE IF EXISTS `z_tmp_1 /* generated by server *

The last DROP TABLE IF EXISTS was killed. The table still exists on the master but the DDL was still logged:

#190731 14:36:55 server id 3119271449 end_log_pos 882519717 CRC32 0xa0c2142c Query	thread_id=2387200	exec_time=3	error_code=1317

SET TIMESTAMP=1564609015/*!*/;

DROP TABLE IF EXISTS `z_tmp_1` /* generated by server */

/*!*/;

It is logged with the query interrupted error (1317), but should it be logged since the table was not removed?

Fix for this issue is implemented in 10.2.27

Sujatha Sivakumar (Inactive) added a comment - 2019-08-14 17:26 Fix for this issue is implemented in 10.2.27

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.

MariaDB Server