hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Slaves that are behind the master no longer cause an error to be logged

Browse Source 
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.
This commit is contained in:
Markus Makela
2016-04-14 12:01:02 +03:00
parent 6988c0bfed
commit bb2d549a00
1 changed files with 0 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
server/modules/routing/binlog/blr_master.c
View File

@ -1953,14 +1953,6 @@ blr_distribute_binlog_record(ROUTER_INSTANCE *router, REP_HEADER *hdr, uint8_t *
slave->binlogfile, slave->binlog_pos, slave->binlogfile, slave->binlog_pos,
hdr->next_pos - hdr->event_size); 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) else if (rotate)
{ {