5a62adc63e
This commit introduces changes that fix the relay master detection that was broken by the merge from 2.1 into 2.2 by commit 1ecd791887994209eb29e56e1271f8c407cd0cdf. In 2.2, the master server ID is used to detect whether a slave is actually replicating from a master. The value is still displayed even if the slave is not actively replicating from a master. The commit in 2.1 causes this value to be stored unconditionally if it is available. By checking the value of Last_IO_Errno and comparing it to a list of known error codes, we know whether the slave is replicating properly. The slave detection in 2.2 correctly identifies a broken slave with a stopped IO thread. Due to this, the test case must be modified to check that the relay master is not a slave if the IO thread is stopped.
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.