• Venkatesh Duggirala's avatar
    Bug#17641586 INCORRECTLY PRINTED BINLOG DUMP INFORMATION · e0efc2c3
    Venkatesh Duggirala authored
    Problem:
    When log_warnings is greater than 1, master prints binlog
    dump thread information in mysqld.1.err file.
    The information contains slave server id, binlog file and
    binlog position. The slave server id is uint32 and the print
    format was wrongly specifified (%d instead of %u).
    Hence a server id which is more than 2 billion is getting
    printed with a negative value.
    Eg: Start binlog_dump to slave_server(-1340259414),
    pos(mysql-bin.001663, 325187493)
    
    Fix: Changed the uint32 format to %u.
    e0efc2c3
sql_repl.cc 62.3 KB