[MXS-1853] Minimal support of MySQL 8 Created: 2018-05-04  Updated: 2018-05-25  Resolved: 2018-05-21

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 2.2.5
Fix Version/s: 2.2.7

Type: New Feature Priority: Major
Reporter: Boden Garman Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None
Environment:

MySQL 8.0.11



 Description   

It seems MaxScale doesn't yet support MySQL 8 correctly - node id, master id and replication depth are all incorrect. Please add support

[root@sql-proxy01 ~]# maxadmin show server mysql04
Server 0x25cf450 (mysql04)
        Server:                              192.168.10.231
        Status:                              Running
        Protocol:                            MySQLBackend
        Port:                                3306
        Server Version:
        Node Id:                             -1
        Master Id:                           -1
        Last event:                          server_up
        Triggered at:                        Fri, 04 May 2018 06:07:26 GMT
        Slave Ids:
        Repl Depth:                          -1
        Number of connections:               0
        Current no. of conns:                0
        Current no. of operations:           0
        Persistent pool size:                0
        Persistent measured pool size:       0
        Persistent actual size max:          0
        Persistent pool size limit:          100
        Persistent max time (secs):          3600
        Connections taken from pool:         0
        Pool availability:                   0.00%

SHOW SLAVE STATUS output

mysql> SHOW SLAVE STATUS\G
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: slave2
                  Master_User: repl
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: mysql-bin.001505
          Read_Master_Log_Pos: 849378490
               Relay_Log_File: overlord-relay-bin.000664
                Relay_Log_Pos: 796836023
        Relay_Master_Log_File: mysql-bin.001504
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes
              Replicate_Do_DB:
          Replicate_Ignore_DB:
           Replicate_Do_Table:
       Replicate_Ignore_Table:
      Replicate_Wild_Do_Table:
  Replicate_Wild_Ignore_Table:
                   Last_Errno: 0
                   Last_Error:
                 Skip_Counter: 0
          Exec_Master_Log_Pos: 796835809
              Relay_Log_Space: 1923122491
              Until_Condition: None
               Until_Log_File:
                Until_Log_Pos: 0
           Master_SSL_Allowed: No
           Master_SSL_CA_File:
           Master_SSL_CA_Path:
              Master_SSL_Cert:
            Master_SSL_Cipher:
               Master_SSL_Key:
        Seconds_Behind_Master: 18479
Master_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 0
                Last_IO_Error:
               Last_SQL_Errno: 0
               Last_SQL_Error:
  Replicate_Ignore_Server_Ids:
             Master_Server_Id: 3
                  Master_UUID: 036f16f4-8cdc-11e5-a40b-cef5953dbfa6
             Master_Info_File: mysql.slave_master_info
                    SQL_Delay: 0
          SQL_Remaining_Delay: NULL
      Slave_SQL_Running_State: Reading event from the relay log
           Master_Retry_Count: 86400
                  Master_Bind:
      Last_IO_Error_Timestamp:
     Last_SQL_Error_Timestamp:
               Master_SSL_Crl:
           Master_SSL_Crlpath:
           Retrieved_Gtid_Set:
            Executed_Gtid_Set:
                Auto_Position: 0
         Replicate_Rewrite_DB:
                 Channel_Name:
           Master_TLS_Version:
       Master_public_key_path:
        Get_master_public_key: 0
1 row in set (0.00 sec)



 Comments   
Comment by markus makela [ 2018-05-21 ]

Treating MySQL 8.0 as if it were 5.7 appears to fix the most obvious problems. The MariaDB specific features do not work (e.g. automated failover).

Comment by markus makela [ 2018-05-25 ]

This means that the old mysql_native_password authentication method must be used.

Generated at Thu Feb 08 04:09:53 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.