RE: Are Ubuntu 64-bit /var/lib/mysql/ibdata (etc) compatible with 32-bit ??
We have a PSE05 Master and PSE06 Slave (PRODUCTION servers) both are Ubuntu 32-bit. We have a third slave PSE07 which is Ubuntu 64-bit. This is our 'live backup' so to speak. We take mysqld down daily on there and tarball the /var/lib/mysql and /var/log/mysql as snapshots (since mysqldump would take a week literally to re-import). Our data is about 100GB and nearly 1 Billion records and growing by several hundred thousand per day. A medium sized installation, but still too big to do a quick dump-n-restore that the mysql docs always suggest. We had some replication hose-up where someone accidentally wrote to the PSE06 slave. This wasn't caught right away and so it cascaded and queued up about 130 rows to be written. Obviously going through this whole business: mysql stop slave; SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1; start slave; show slave status\G Would take WAY too long and painful. Painful for 130 rows? Script it ... check show slave status, and if replication is off execute SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1; start slave; So is this even possible. Are the ibdata files binary compatible between bit versions (or even different OS's for that matter) Its safe, but this is not the way to fix your problem. You should use Maatkit mk-table-checksum and mk-table-sync: http://www.maatkit.org/doc/mk-table-checksum.html http://www.maatkit.org/doc/mk-table-sync.html We are getting errors: 101013 23:56:22 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=mysqld-relay-bin' to avoid this problem.^M Probably you didn't set log-bin in my.cnf with a value? HTH, ds -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Are Ubuntu 64-bit /var/lib/mysql/ibdata (etc) compatible with 32-bit ??
We have a PSE05 Master and PSE06 Slave (PRODUCTION servers) both are Ubuntu 32-bit. We have a third slave PSE07 which is Ubuntu 64-bit. This is our 'live backup' so to speak. We take mysqld down daily on there and tarball the /var/lib/mysql and /var/log/mysql as snapshots (since mysqldump would take a week literally to re-import). Our data is about 100GB and nearly 1 Billion records and growing by several hundred thousand per day. We had some replication hose-up where someone accidentally wrote to the PSE06 slave. This wasn't caught right away and so it cascaded and queued up about 130 rows to be written. Obviously going through this whole business: mysql stop slave; SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1; start slave; show slave status\G Would take WAY too long and painful. So we thought we'd shut down PSE06, scp the .tgz file from PSE07, dump it in, set the pointers on the slave and let replication catch up. Not so much. So is this even possible. Are the ibdata files binary compatible between bit versions (or even different OS's for that matter) We are getting errors: 101013 23:56:22 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=mysqld-relay-bin' to avoid this problem.^M r...@pse06:~# find /home/mysql/ | grep relay /home/mysql/mysqld-relay-bin.01 /home/mysql/relay-log.info /home/mysql/mysqld-relay-bin.05 /home/mysql/binlog/mysqld-relay-bin.004055 /home/mysql/binlog/mysqld-relay-bin.004287 /home/mysql/binlog/mysqld-relay-bin.005693 /home/mysql/binlog/mysqld-relay-bin.004041 /home/mysql/binlog/mysqld-relay-bin.004676 /home/mysql/binlog/mysqld-relay-bin.004664 /home/mysql/binlog/mysqld-relay-bin.004044 /home/mysql/binlog/mysqld-relay-bin.004468 /home/mysql/binlog/mysqld-relay-bin.004682 /home/mysql/binlog/mysqld-relay-bin.004094 /home/mysql/binlog/mysqld-relay-bin.004153 /home/mysql/binlog/mysqld-relay-bin.004051 /home/mysql/binlog/mysqld-relay-bin.004645 /home/mysql/binlog/mysqld-relay-bin.004516 /home/mysql/binlog/mysqld-relay-bin.003889 /home/mysql/binlog/mysqld-relay-bin.004715 /home/mysql/binlog/mysqld-relay-bin.004299 /home/mysql/binlog/mysqld-relay-bin.004483 /home/mysql/binlog/mysqld-relay-bin.004628 /home/mysql/binlog/mysqld-relay-bin.004088 /home/mysql/binlog/mysqld-relay-bin.004059 /home/mysql/binlog/mysqld-relay-bin.index /home/mysql/binlog/mysqld-relay-bin.004271 /home/mysql/binlog/mysqld-relay-bin.004077 /home/mysql/binlog/mysqld-relay-bin.004671 /home/mysql/binlog/mysqld-relay-bin.004513 /home/mysql/binlog/mysqld-relay-bin.004732 /home/mysql/binlog/mysqld-relay-bin.004096 /home/mysql/mysqld-relay-bin.06 /home/mysql/mysqld-relay-bin.08 /home/mysql/mysqld-relay-bin.02 /home/mysql/mysqld-relay-bin.03 /home/mysql/mysqld-relay-bin.04 /home/mysql/mysqld-relay-bin.07 /home/mysql/mysqld-relay-bin.10 /home/mysql/mysqld-relay-bin.index /home/mysql/mysqld-relay-bin.12 /home/mysql/mysqld-relay-bin.13 /home/mysql/mysqld-relay-bin.09 /home/mysql/mysqld-relay-bin.11 Oct 13 23:55:27 pse06 mysqld[9185]: 101013 23:55:27 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=mysqld-relay-bin' to avoid this problem. Oct 13 23:55:27 pse06 mysqld[9185]: 101013 23:55:27 [ERROR] Failed to open the relay log '/home/mysql/binlog/mysqld-relay-bin.005693' (relay_log_pos 53058571) Oct 13 23:55:27 pse06 mysqld[9185]: 101013 23:55:27 [ERROR] Could not find target log during relay log initialization -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
