I also ran into the bug when testing an upgrade from percona-5.5 to 5.6. And like the previous commenter I reinstalled from a clean slate and imported our data from a .sql file. Is it possible that we only trigger this bug when replicating from 5.5 to 5.6?
I also ran into the bug when testing an upgrade from percona-5.5 to 5.6. And like the previous commenter I reinstalled from a clean slate and imported our data from a .sql file. Is it possible that we only trigger this bug when replicating from 5.5 to 5.6?