5fa3ef8236
Earlier, by default, the error and message logfiles were written to the filesystem and trace and debug logfiles to shared memory. Now, with just one log-file the default must be the file-system. However, if info and debug messages are logged, then the filesystem will become a bottle-neck. A reasonable approach is then as follows (in the config file) syslog=true maxlog=false log_to_shm=true With this set, the maxlog file will be created to shared memory, but nothing will be written to it, since it is disabled. However, if there is a need to investigate something, then a dba can from maxadmin turn on maxlog logging and also enable info and debug messages. That is, it will be possible to enable debugging output without restarting maxscale. Incidentally, the way the config file and command line arguments are handled should be rewritten. Currently, it is a mess.
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. Send email to maxscale@googlegroups.com or use the forum interface
Bugs can be reported in the MariaDB Corporation bugs database https://mariadb.atlassian.net/projects/MXS/issues
Documentation
For information about installing and using MaxScale, please refer to the documentation.