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

Lost connection to master server while waiting for a result. Connection has been idle for 0.0 seconds

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Won't Fix
    • 2.5.13
    • N/A
    • Core
    • None
    • Debian 10.10, 10.5.11-MariaDB
    • MXS-SPRINT-136

    Description

      Hello,

      I'm experiencing theses warnings in MX's log every seconds.

      I tried disabling persistent pool without success. I've also added backend timeouts without success. No success with setting a higher wait_timeout on mariadb either.

      My configuration is a read-write split router and 3x 10.5.11-MariaDB galera cluster nodes.

      With info_log enabled I get the following :

      2021-07-01 12:45:27   info   : Stopped RW2 client session [227]
      2021-07-01 12:45:27   info   : (228) (RW2) > Autocommit: [enabled], trx is [not open], cmd: (0x03) COM_QUERY, plen: 13, type: QUERY_TYPE_READ, stmt: SELECT 1
      2021-07-01 12:45:27   info   : (228) [readwritesplit] (RW2) Route query to slave: marianode3 <
      2021-07-01 12:45:27   info   : (228) [readwritesplit] (RW2) Reply complete, last reply from marianode3
      2021-07-01 12:45:27   info   : (228) [qc_sqlite] (RW2) Parsing the query failed, cannot report query type: KILL CONNECTION_ID();
      2021-07-01 12:45:27   info   : (228) [qc_sqlite] (RW2) Parsing the query failed, cannot report query operation: KILL CONNECTION_ID();
      2021-07-01 12:45:27   info   : (228) [qc_sqlite] (RW2) Parsing the query failed, cannot report query operation: KILL CONNECTION_ID();
      2021-07-01 12:45:27   info   : (228) (RW2) > Autocommit: [enabled], trx is [not open], cmd: (0x03) COM_QUERY, plen: 26, type: , stmt: KILL CONNECTION_ID();
      2021-07-01 12:45:27   info   : (228) [readwritesplit] (RW2) Route query to master: marianode1 <
      2021-07-01 12:45:27   info   : (228) [readwritesplit] (RW2) Master 'marianode1' failed: #HY000: Lost connection to backend server: connection closed by peer (marianode1)
      2021-07-01 12:45:27   error  : (228) [readwritesplit] (RW2) Lost connection to the master server, closing session. Lost connection to master server while waiting for a result. Connection has been idle for 0 seconds. Error caused by: #HY000: Lost connection to backend server: connection closed by peer (marianode1). Last close reason: <none>. Last error:
      

      My MX configuration :

      [maxscale]
      threads=auto
      #log_notice=1
      #log_debug=1
      #log_info=1
      syslog=false
      auth_connect_timeout=3s
      auth_read_timeout=3s
      auth_write_timeout=3s
       
      [MySQLMonitorLocal]
      type=monitor
      module=galeramon
      servers=marianode1,marianode2,marianode3
      user=maxscale
      password=hidden
      monitor_interval=1000
      backend_connect_timeout=3s
      backend_write_timeout=3s
      backend_read_timeout=3s
       
       
      # =============== Services ================ #
       
      [RW2]
      type=service
      router=readwritesplit
      # deprecated
      #localhost_match_wildcard_host=1
      servers=marianode1,marianode2,marianode3
      max_slave_connections=2
      user=maxscale
      password=hidden
      max_connections=350
      strip_db_esc=true
       
      # ===============  Listeners ================ #
       
      [RWListenerLocal]
      type=listener
      service=RW2
      protocol=MariaDBClient
      port=3310
      address=127.0.0.1
       
      [RWListenerLocalSocket]
      type=listener
      service=RW2
      protocol=MariaDBClient
      socket=/var/lib/maxscale/rwsplit.sock
       
      # =============== Servers ================ #
      [marianode1]
      type=server
      address=10.100.20.50
      port=3306
      protocol=MariaDBBackend
      #persistpoolmax=100
      #persistmaxtime=60s
      #rank=primary
       
      [marianode2]
      type=server
      address=10.100.20.51
      port=3306
      protocol=MariaDBBackend
      #persistpoolmax=100
      #persistmaxtime=60s
      #rank=secondary
       
      [marianode3]
      type=server
      address=10.100.20.52
      port=3306
      protocol=MariaDBBackend
      #persistpoolmax=100
      #persistmaxtime=60s
      #rank=primary
      

      Do you have any clues why this happening with latest version ?

      Attachments

        Activity

          People

            markus makela markus makela
            jom Maiavria
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.