Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-2331

Slave server 'server2': response (0xff) differs from master's response (0x00) to COM_QUERY

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Duplicate
    • Affects Version/s: 2.3.4
    • Fix Version/s: N/A
    • Component/s: readwritesplit
    • Environment:
      CentOS Linux release 7.6.1810 (Core)

      # yum list installed | grep maxscale
      maxscale.x86_64 2.3.4-1 @mariadb-maxscale

      Description

      [Galera Service]
      type=service
      router=readwritesplit
      servers=server1,server2
      user=maxscale
      passwd=maxscale
      enable_root_user=1
      use_sql_variables_in=master
      #disable_sescmd_history=true
      #master_accept_reads=true
      #strict_multi_stmt=true

      /var/log/messages:
      Feb 14 16:07:04 scsmondb18ms maxscale[15836]: (6) Slave server 'server2': response (0xff) differs from master's response (0x00) to COM_QUERY: `use centreon`. Closing slave connection due to inconsistent session state.
      Feb 14 16:07:04 scsmondb18ms maxscale[15836]: (6) Router session exceeded session command history limit. Server reconnection is disabled and only servers with consistent session state are used for the duration ofthe session. To disable this warning and the session command history, add `disable_sescmd_history=true` to service 'Galera-Service'. To increase the limit (currently 50), add `max_sescmd_history` to the same service and increase the value.
      Feb 14 16:07:09 scsmondb18ms maxscale[15836]: (7) Slave server 'server2': response (0xff) differs from master's response (0x00) to COM_QUERY: `/*!40101 SET character_set_client = @saved_cs_client */;`. Closing slave connection due to inconsistent session state.
      Feb 14 16:07:14 scsmondb18ms maxscale[15836]: (10) Slave server 'server2': response (0xff) differs from master's response (0x00) to COM_QUERY: `/*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */;`. Closing slave connection due to inconsistent session state.

      I've remark options:
      disable_sescmd_history=true
      master_accept_reads=true
      strict_multi_stmt=true

      Because in this case, error messages just suppressed, but the issue still exists.

      I saw closed bug MXS-2079, but it appears again.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              markus makela markus makela
              Reporter:
              Acid_Scorpion Dmitry Petrich
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: