Skip to content
Switch branches/tags

Latest commit

The command stored in m_reply is not updated for buffers marked as
ignorable. If the ping triggered by connection_keepalive is done right
after a COM_CHANGE_USER, the value of m_reply.command() would contain the
COM_CHANGE_USER which triggered an extra COM_CHANGE_USER to be sent. As
this code was before the code that incremented the number of ignored
replies, the reply was not ignored and triggered the debug assertion.


Failed to load latest commit information.
Latest commit message
Commit time

MaxScale by MariaDB Corporation

Build Status

The MariaDB Corporation MaxScale is an intelligent proxy that allows forwarding of database statements to one or more database servers using complex rules, a semantic understanding of the database statements and the roles of the various servers within the backend cluster of databases.

MaxScale is designed to provide load balancing and high availability functionality transparently to the applications. In addition it provides a highly scalable and flexible architecture, with plugin components to support different protocols and routing decisions.

For a detailed overview of what MaxScale can do, read the MaxScale page on the MariaDB website.

An Google Group exists for MaxScale that can be used to discuss ideas, issues and communicate with the MaxScale community.

We're also on the #maria and #maxscale channels on FreeNode.

Please report all feature requests, improvements and bugs in the MariaDB Jira.

Getting Started

Read the Documentation Overview for a list of all MaxScale documents.


The official documentation can be found on the MariaDB Knowledge Base.

A MaxScale Troubleshooting Guide can be found on the MariaDB Knowledgebase. It answers common questions encountered when installing and using MaxScale.

The documentation can also be found in the Documentation directory of the source tree.

Contributing Code

Read the Contributing page on the wiki for more information on how to do pull request and where to do them.