Thanks again Reindl,
I am not disagree with you.
I am afraid l am not the only one how would be interested if there are any plans to make this kind of mix replication working.
Am 16.02.2015 um 22:53 schrieb Vadim Pestovnikov:
Thank you Reindl.
So basically what that means is that mariadb is not 100% compatable with
percona and mysql?
define 100% - replication is a *binary log*
if it would be identical in every aspect it would exist only one product and even if all docs pretend 100% compatibility i would never come to the idea even run different minor versions in a replication setup
just follow these instructions leads to the conclusion mix different products is a bad idea: http://dev.mysql.com/doc/refman/5.0/en/replication-upgrade.html
P.S.: i don't appreciate off-list replies
On Feb 16, 2015 1:23 PM, "Reindl Harald" <h.reindl@thelounge.net
<mailto:h.reindl@thelounge.net>> wrote:
Am 16.02.2015 um 22:19 schrieb Vadim Pestovnikov:
Error in Log_event::read_log_event(): 'Found invalid event in binary
log', data_len: 44, event_type: 33
Error reading relay log event: slave SQL thread aborted because
of I/O error
My slave is MariaDB 10 with data and logs partitions encrypted
by LUKS
and with SSL enabled. As far as RDS and Percona servers don't
use SSL I
am using non SSL user for the replication.
Any recommendations or suggestions would be extremely appreciated
don't mix different server versions in replication setups
there is a good reason why it is recommended always to update first
the slaves, run "mysql_upgrade" and then the masters to be 100% sure
that the maste rnever don't write anything into the binlog the slave
won't understand because differences in details
_______________________________________________
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help : https://help.launchpad.net/ListHelp