I have set up two replication slaves, one on CentOS(x86_64 5.1.37), the other on Ubuntu LTS(x86_64 mysql 5.5.38). Both of them seem to replicate most of the Master db (CentOS i686, mysql 5.5.37) correctly, except for one column in a table.
The problematic column was created as
int(11) DEFAULT NULL, recording time stamps in Unix epoch, which should not have reached year 2038 yet. However, when I tried to compare data in the Master and Slave, I found recently replicated rows on Slaves have turned into
2147483647, or INT32_MAX. BTW, this is not the case for the Master.
Is binary log format architecture specific? How can I resolve this? Or at least make sure that the DB on Slaves would not record any more abnormal timestamps once switched into Master?