Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-6242

Some but not all slaves do character set mangling

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 10.0.10
    • Fix Version/s: 10.0.11
    • Component/s: None
    • Labels:
      None
    • Environment:
      Linux,RHEL6

      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

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              knielsen Kristian Nielsen
              Reporter:
              arjen Arjen Lentz
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Git Integration