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

Connection loss problem on maxscale

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Cannot Reproduce
    • 2.5.8
    • N/A
    • N/A
    • None
    • I have a maxscale instance maxscale01 and three MySQL instances, mysql01 (Master) mysql02 (slave01) mysql03 (slave02)

    Description

      I have a maxscale instance maxscale01 which version is v2.2.22 and three MySQL instances, mysql01 (Master) mysql02 (slave01) mysql03 (slave02)
      I found that when I use MySQL -uqfsys -p -h${maxscale_IP} - p ${port}, and keep a long connection.
      At this point, there is a session from the qfsys account on each MySQL back end, and a long connection is maintained.
      When I repeatedly execute a `select 1` as heartbeat detection on the client for a long time, the request is continuously forwarded to mysql01, and the qfsys session time on mysql01 is refreshed.
      I use a long connection on the client, there has a problem that session wait_timeout in MySQL. When my session from the library times out, I execute a large-scale query on the client, and these requests are forwarded to slave01. Since the session of qfsys on slave01 has timed out, I will prompt the client for lost connection to MySQL.
      I don't want to increase that value of wait_timeout
      Does maxscale have any configuration or method to solve this problem?

      My profile is as follows:

      proxy_protocol=1
      [server-0]
      type=server
      address=test-cbdd100-headless
      port=3306
      protocol=MariaDBBackend
       
      [server-1]
      type=server
      address=test-cbdd101-headless
      port=3306
      protocol=MariaDBBackend
       
      [server-2]
      type=server
      address=test-cbdd110-headless
      port=3306
      protocol=MariaDBBackend
       
      [server-3]
      type=server
      address=test-cbdd111-headless
      port=3306
      protocol=MariaDBBackend
       
      [MariaDB-Monitor]
      type=monitor
      module=mysqlmon
      servers=server-0,server-1,server-2,server-3
      user=root
      passwd=$MYSQL_ROOT_PASSWORD
      monitor_interval=1000
       
      [Read-Only-Service]
      type=service
      router=readconnroute
      servers=server-0,server-1,server-2,server-3
      user=root
      passwd=$MYSQL_ROOT_PASSWORD
      enable_root_user=1
       
      [Read-Write-Service]
      type=service
      router=readwritesplit
      servers=server-0,server-1,server-2,server-3
      user=root
      passwd=$MYSQL_ROOT_PASSWORD
      enable_root_user=1
      master_accept_reads=true
      use_sql_variables_in=master
       
      [MaxAdmin-Service]
      type=service
      router=cli
       
      [Read-Only-Listener]
      type=listener
      service=Read-Only-Service
      protocol=MariaDBClient
      port=4008
       
      [Read-Write-Listener]
      type=listener
      service=Read-Write-Service
      protocol=MariaDBClient
      port=4006
       
      [MaxAdmin-Listener]
      type=listener
      service=MaxAdmin-Service
      protocol=maxscaled
      socket=default
      

      Attachments

        Activity

          People

            Unassigned Unassigned
            chenhao haooy chen
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.