meta user
network profile
| bio | website | lourdas.name |
|---|---|---|
| location | Thessaloniki, Greece | |
| age | 35 | |
| visits | member for | 2 years, 2 months |
| seen | 2 days ago | |
| stats | profile views | 7 |
|
2d |
awarded | Caucus |
|
Feb 22 |
comment |
Should master and slave have same mysql version? You shouldn't worry much. As I said, test before using 5.5.30. If you can run this setup for some time, you will have more confidence that the different versions solution works fine (for your setup always). I guess you cannot upgrade the master to 5.5.30, this would be the best option. |
|
Feb 22 |
answered | Should master and slave have same mysql version? |
|
Jan 20 |
awarded | Scholar |
|
Jan 20 |
accepted | MariaDB and XtraDB/InnoDB plugins |
|
Jan 20 |
comment |
MariaDB and XtraDB/InnoDB plugins You're right. I've just issued the command and it shows: | InnoDB | DEFAULT | XtraDB engine based on InnoDB plugin. Supports transactions, row-level locking, and foreign keys | YES | YES | YES | |
|
Jan 19 |
awarded | Editor |
|
Jan 19 |
revised |
MariaDB and XtraDB/InnoDB plugins Minor typo |
|
Oct 11 |
awarded | Tumbleweed |
|
Oct 4 |
asked | MariaDB and XtraDB/InnoDB plugins |
|
Jun 22 |
awarded | Teacher |
|
Jun 12 |
comment |
MySQL Error Reading Communication Packets Very good explanation. |
|
Jun 12 |
answered | Can MySQL be patched |
|
Jun 3 |
comment |
MySQL lost records in a master slave scheme No problem, don't worry about it. :-) |
|
Jun 3 |
comment |
MySQL lost records in a master slave scheme We are already using the InnoDB plugin (I said it in my initial question) and as I recall, the InnoDB log buffer size is set to 48M, so both your suggestions were already set from the beginning. Thanks. |
|
Jun 3 |
answered | MySQL replication fails due to duplicate keys after master is restarted |
|
Jun 3 |
answered | How to write a shell script to check the mysql database backup status. |
|
Jun 3 |
answered | Design the database of an existing application |
|
Jun 3 |
comment |
MySQL lost records in a master slave scheme Hi, thanks for your detailed answer and sorry for the delay to reply. At the moment, I can't upgrade to MySQL 5.5, because I'm using the stable Debian Squeeze branch. Maybe when Debian 7.0 is released, the upgrade will probably be possible. What I did is to reinstall Debian in a new machine and delete all files from /var/lib/mysql and re-create from scratch (using MySQL 5.1.61). We created a batch test script to simulate the insertion procedure and this time, no records were lost. It seems that the issue went away. Thanks. |
|
May 7 |
awarded | Supporter |
