[MDEV-6242] Some but not all slaves do character set mangling Created: 2014-05-15  Updated: 2014-06-03  Resolved: 2014-06-03

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 10.0.10
Fix Version/s: 10.0.11

Type: Bug Priority: Major
Reporter: Arjen Lentz Assignee: Kristian Nielsen
Resolution: Duplicate Votes: 0
Labels: None
Environment:

Linux,RHEL6


Issue Links:
Duplicate
duplicates MDEV-6156 Parallel replication incorrectly cach... Closed

 Description   

Setup: dual master (probably not relevant), N slaves, everything MariaDB 10.0.10
All servers essentially the same config (copies from same source with only server specifics changed)
Binlog format MIXED
InnoDB engine
Parallel replication enabled
All charset settings utf8

Table/column utf8.

utf8 string inserted on active master, reads back ok.
On other master (acting as slave), incorrect (charset mangling)
On some slaves, OK
On other slaves, incorrect

Which slaves get a string incorrect changes per row, so it's not always the same ones.

Interesting isn't it?

Verified by doing SELECT SHA1() on the affect column, to rule out any client mangling.

SELECT string, SHA1(string) FROM t\G

Correct:

string: Atlético Madrid
SHA1(string): 6dec52f694515702664a20b7660574139267a46a

Incorrect:

string: Atlético Madrid
SHA1(string): db4bb2aa6aae25ce19e0dda3626d37fa356c673e



 Comments   
Comment by Arjen Lentz [ 2014-05-15 ]

I realise that because of the setup this one might be tricky to reproduce.
At this point I'm particularly interested in possible ideas on how this issue could occur, as that might also help me devise a setup to reproduce the issue in an isolated environment.

Comment by Arjen Lentz [ 2014-05-15 ]

knielsen (IRC) reckons it could be a case of https://mariadb.atlassian.net/browse/MDEV-6156

I'll upgrade a few of the slaves to 10.0.11 to see.

Comment by Arjen Lentz [ 2014-05-16 ]

Provisionally, the upgrade to 10.0.11 appears to have resolved the issue - no new discrepancies have been spotted since the upgrade. We'll keep an eye on it just to be sure.
So, I'll mark this issue as a dup of MDEV-6156 as it appears to have been the same bug.

thanks for your quick assistance, Kristian!

Generated at Thu Feb 08 07:10:24 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.