IO thread on crash safe replication uses older binary coordinates after slave server restarts after a crash
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Invalid
|
Undecided
|
Unassigned | ||
5.1 |
Invalid
|
Undecided
|
Unassigned | ||
5.5 |
Expired
|
High
|
Unassigned | ||
5.6 |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Tested on VirtualBox VM running MySQL Sandbox:
Crash resistant replication enabled:
innodb_
Ran this on master:
mysql --port=22987 < employees.sql
Turned off VirtualBox, turned it on and started MySQL slave instances. Relevant error log below:
InnoDB: Warning: innodb_
InnoDB: relay-log.info is detected.
InnoDB: relay log: position 39469633, file name ./mysql_
InnoDB: master log: position 39469487, file name mysql-bin.000003
***
InnoDB: In a MySQL replication slave the last master binlog file
InnoDB: position 40495923, file name mysql-bin.000003
InnoDB: and relay log file
InnoDB: position 40496069, file name ./mysql_
***
131015 7:16:07 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000003' at position 40495923, relay log './mysql_
131015 7:16:07 [Note] Slave I/O thread: connected to master 'rsandbox@
Note:
Tried to kill mysql slave instances with kill -9 and kill -11 but could not reproduce it so I tried turning of Virtual Box instead.
summary: |
IO thread on crash safe replication uses older binary coordinates after - slave server restarts + slave server restarts after a crash |
tags: | added: i41005 |
tags: | added: crash-resistant-slave-5.5 |
Trying to reproduce this particular issue on current PS 5.5 trunk (revno 588) and continually hit a different bug that I reported as 1243953. I can't seem to reproduce this exactly as described above ut that is likely just due to timing differences.