[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: |
|
||||||||
| Description |
|
Setup: dual master (probably not relevant), N slaves, everything MariaDB 10.0.10 Table/column utf8. utf8 string inserted on active master, reads back ok. 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 Incorrect: string: Atlético Madrid |
| Comments |
| Comment by Arjen Lentz [ 2014-05-15 ] |
|
I realise that because of the setup this one might be tricky to reproduce. |
| 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. thanks for your quick assistance, Kristian! |