7e17e2cd56
The polling mechanism can now optionally be used for managing the lifetime of an object placed into the poll set. If a MXS_POLL_DATA has a non-null 'free', then the reference count of the data will be increased before calling the handler and decreased after. In that case, if the reference count reaches 0, the free function will be called. Note that the reference counts of *all* MXS_POLL_DATAs returned by 'epoll_wait' will be increased before the events are delivered to the handlers individually for each MXS_POLL_DATA, and then once all events have been delivered, the reference count of each MXS_POLL_DATA will be decreased. This ensure that if there are interdependencies between different MXS_POLL_DATAs returned by one call to 'epoll_wait', the case that an MXS_POLL_DATA is deleted before its events have been delivered can be avoided by using the reference count for lifetime management. In subsequent commits, the reference count will be taken into use in the lifetime management of DCBs.
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.