From bb2d549a0073a606e6976ffd73d30ebb12283b81 Mon Sep 17 00:00:00 2001 From: Markus Makela Date: Thu, 14 Apr 2016 12:01:02 +0300 Subject: [PATCH] Slaves that are behind the master no longer cause an error to be logged When a slave transitions from catchup mode to up-to-date mode, an error message is logged because the slave is at an unexpected position. This error message should not be logged because it is a possible and an expected situation. --- server/modules/routing/binlog/blr_master.c | 8 -------- 1 file changed, 8 deletions(-) diff --git a/server/modules/routing/binlog/blr_master.c b/server/modules/routing/binlog/blr_master.c index a95851cff..977888e3f 100644 --- a/server/modules/routing/binlog/blr_master.c +++ b/server/modules/routing/binlog/blr_master.c @@ -1953,14 +1953,6 @@ blr_distribute_binlog_record(ROUTER_INSTANCE *router, REP_HEADER *hdr, uint8_t * slave->binlogfile, slave->binlog_pos, hdr->next_pos - hdr->event_size); } - else - { - MXS_ERROR("Slave %s:%d server ID %d is at position %u when " - "it should be at %u. Binlog file is '%s'.", slave->dcb->remote, - ntohs((slave->dcb->ipv4).sin_port), slave->serverid, - slave->binlog_pos, hdr->next_pos - hdr->event_size, - slave->binlogfile); - } } else if (rotate) {