Markus Mäkelä ef2ee38ccf MXS-1446: Store more detailed event information
The timestamp of the last change from passive to active is now
tracked. This, with the timestamps of the last master_down and master_up
events, allows detection of cases when MaxScale was failed over but the
failover was not done.

Currently, only a warning is logged if no new master has appeared within
90 seconds of a master_down event and MaxScale was set to active from
passive.

The last event and when the event was triggered is now shown for all
servers. The latest change from passive to active is also shown.
2017-09-27 19:32:58 +03:00
2017-07-03 17:08:39 +03:00
2017-09-20 10:47:53 +03:00
2017-09-14 15:30:44 +03:00
2017-09-12 11:17:19 +03:00
2017-09-27 13:04:14 +03:00
2017-09-21 09:36:50 +03:00
2017-06-01 10:24:20 +03:00
2017-06-01 10:24:20 +03:00
2017-05-23 21:09:30 +03:00
2017-05-29 21:50:29 +03:00
2017-08-17 15:02:16 +03:00
2017-06-01 19:39:41 +03:00
2017-06-01 10:42:21 +03:00
2017-04-20 16:03:41 +03:00
2017-06-20 10:45:02 +03:00
2017-09-26 10:44:19 +03:00
2017-06-20 11:11:18 +03:00

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.

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.

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.

Description
No description provided
Readme 118 MiB
Languages
C 50.9%
C++ 30.8%
Shell 3.7%
HTML 3.2%
Tcl 3.1%
Other 8.1%