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

Non-critical errors in binlogrouter are now properly logged as warnings

Browse Source 
The event distribution error messages were not truly errors but only rare
corner cases that usually don't happen. This doesn't mean that they should
be treated as errors and treating them as warnings is more helpful.
This commit is contained in:
Markus Makela 2016-04-15 10:37:21 +03:00
parent aabcc4fb12
commit 2855389fe2
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -1935,7 +1935,7 @@ blr_distribute_binlog_record(ROUTER_INSTANCE *router, REP_HEADER *hdr, uint8_t *
else if (rotate)
{
/** Slave is more than one binlog file behind */
MXS_ERROR("Slave %s:%d server ID %d is behind more than one binlog file "
MXS_WARNING("Slave %s:%d server ID %d is behind more than one binlog file "
"from the master. Slave is using '%s' with position %d "
"when master binlog file is '%s'.", slave->dcb->remote,
ntohs((slave->dcb->ipv4).sin_port), slave->serverid,
@ -1944,7 +1944,7 @@ blr_distribute_binlog_record(ROUTER_INSTANCE *router, REP_HEADER *hdr, uint8_t *
else
{
/** Slave is lagging behind */
MXS_ERROR("Slave %s:%d server ID %d is using binlog file '%s' with "
MXS_WARNING("Slave %s:%d server ID %d is using binlog file '%s' with "
"position %d. Master binlog file is '%s' at position %lu "
"with last safe event at %lu.", slave->dcb->remote,
ntohs((slave->dcb->ipv4).sin_port), slave->serverid,