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

debug assert at rwsplit_route_stmt.cc:469 failed: btype != BE_MASTER

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Fixed
    • None
    • 2.3.4
    • readwritesplit
    • None

    Description

      The following debug assertion:

      debug assert at /home/markusjm/MaxScale/server/modules/routing/readwritesplit/rwsplit_route_stmt.cc:469 failed: btype != BE_MASTER
      

      caused by:

      BEGIN;
      SELECT @@server_id;
      COMMIT;
      

      with config that routes all statements to server2:

      [maxscale]
      threads=4
       
      [server1]
      type=server
      address=127.0.0.1
      port=3000
      protocol=MySQLBackend
       
      [server2]
      type=server
      address=127.0.0.1
      port=3001
      protocol=MySQLBackend
       
      [MySQL-Monitor]
      type=monitor
      module=mariadbmon
      servers=server1,server2
      user=maxuser
      passwd=maxpwd
      monitor_interval=10000
       
      [Read-Write-Service]
      type=service
      router=readwritesplit
      servers=server1,server2
      user=maxuser
      passwd=maxpwd
      max_slave_connections=100%
      enable_root_user=1
      filters=NamedServerFilter
       
      [Read-Write-Listener]
      type=listener
      service=Read-Write-Service
      protocol=MySQLClient
      port=4006
       
      [NamedServerFilter]
      type=filter
      module=namedserverfilter
      match01=^.*$
      target01=server2
      user=maxuser
      

      Attachments

        Activity

          People

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