872a51a376
With the changes in this commit it is possible to add and remove MaxScale specific user variables. A MaxScale specific user variable is a user variable that is interpreted by MaxScale and that potentially changes the behaviour of MaxScale. MaxScale specific user variables are of the format "@maxscale.x.y" where "@maxscale" is a mandatory prefix, x a scope identifying the component that handles the variable and y the component specific variable. So, a variable might be called e.g. "@maxscale.cache.enabled". The scope "core" is reserved (although not enforced yet) to MaxScale itself. The idea is that although MaxScale catches these, they are passed through to the server. The benefit of this is that we do not need to detect e.g. "SELECT @maxscale.cache.enabled", but can let the result be returned from the server. The interpretation of a provided value is handled by the component that adds the variable. In a subsequent commit, it will be possible for a component to reject a value, which will then cause an error to be returned to the client. There are 3 new functions: - session_add_variable() using which a variable is added, - session_remove_variable() using which a variable is removed, and - session_set_variable_value(). The two former ones are to be called by components, the last one by the protocol that catches the "set @maxscale..." statements.
MaxScale by MariaDB Corporation
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.
MaxScale is implemented in C and makes extensive use of the asynchronous I/O capabilities of the Linux operating system. The epoll system is used to provide the event driven framework for the input and output via sockets.
The protocols are implemented as external shared object modules which can be loaded at runtime. These modules support a fixed interface, communicating the entries points via a structure consisting of a set of function pointers. This structure is called the "module object".
The code that routes the queries to the database servers is also loaded as external shared objects and are referred to as routing modules.
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.
Documentation
For information about installing and using MaxScale, please refer to the documentation. The official documentation can be found on the MariaDB Knowledge Base.
- MariaDB MaxScale 2.1 Documentation
- MariaDB MaxScale 2.0 Documentation
- MariaDB MaxScale 1.4 Documentation
The module and configuration documentation can 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.