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

Packet received out-of-order. Expected 1; got 0

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 2.2.16
    • 2.2.20
    • readconnroute
    • None
    • MXS-SPRINT-70

    Description

      Folks,

      I've seen this happening again on 2.2.16. We worked together some time ago and sorted that out but, using the ReadWriteSplut Router; not sure if the ReadConnRouter, being used this way, also has some similar code to create this situation. This below error was happening when running 2.2.16:

      Packet received out-of-order. Expected 1; got 3
      

      So, we downgraded Maxscale to 2.2.4, and then, the error stopped occurring. Interesting is that we didn't change anything in the configuration file, just replace the .deb package. Below, the configurations in use:

      [maxscale]
      threads=auto
      log_augmentation=1
      ms_timestamp=1
      log_info=0
       
      #: maxctrl
      admin_host=0.0.0.0
      admin_port=8989
      admin_auth=1
      admin_log_auth_failures=1
       
      [replication-cluster-monitor]
      type=monitor
      module=mariadbmon
      user=maxmon
      password=80071DBFF3A797CD2E453845F8781BB3BD1E8D12FB1F7604A12B86F9FA18BF93
      monitor_interval=5000
      backend_connect_timeout=3
      backend_write_timeout=2
      backend_read_timeout=1
      backend_connect_attempts=1
      journal_max_age=28800
      script_timeout=90
      servers=mariadb01,mariadb02,mariadb03
      servers_no_promotion=gtprd-mariadb03
      auto_rejoin=true
      auto_failover=true
      failcount=5
      replication_password=14F9823438455408191AC3CBA100C54B4984B1D24F8E1099301B4F15FBD7807C
      replication_user=mariadb
      detect_replication_lag=false
      detect_stale_master=true
      detect_stale_slave=true
      mysql51_replication=false
      multimaster=false
      detect_standalone_master=true
      allow_cluster_recovery=true
      ignore_external_masters=false
      events=master_down,master_up,slave_down,slave_up,server_down,server_up,synced_down,synced_up,donor_down,donor_up,ndb_down,ndb_up,lost_master,lost_slave,lost_synced,lost_donor,lost_ndb,new_master,new_slave,new_synced,new_donor,new_ndb
      failover_timeout=90
      switchover_timeout=90
      verify_master_failure=true
      master_failure_timeout=10
       
      [readconn-service-master]
      type=service
      router=readconnroute
      router_options=master
      servers=mariadb01,mariadb02,mariadb03
      user=maxuser
      password=F1105B285F8FF06817A58459887038431CEDAAFA9575EEDBD91CBA0095E3E3F1
       
      [readconn-listener-master]
      type=listener
      service=readconn-service-master
      protocol=MariaDBClient
      port=3306
       
      [mariadb01]
      type=server
      protocol=mariadbbackend
      address=10.81.21.11
      port=3306
      authenticator=MySQLBackendAuth
       
      [mariadb02]
      type=server
      protocol=mariadbbackend
      address=10.81.21.12
      port=3306
      authenticator=MySQLBackendAuth
       
      [mariadb03]
      type=server
      protocol=mariadbbackend
      address=10.81.21.13
      port=3306
      authenticator=MySQLBackendAuth
       
      [CLI]
      type=service
      router=cli
       
      [CLI-Unix-Listener]
      type=listener
      service=CLI
      protocol=maxscaled
      socket=default
       
      [CLI-Inet-Listener]
      type=listener
      service=CLI
      protocol=maxscaled
      address=localhost
      port=6603
      

      Similar case is https://jira.mariadb.org/browse/MXS-1734

      Thanks!

      Attachments

        Issue Links

          Activity

            People

              markus makela markus makela
              wagnerbianchi Wagner Bianchi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 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.