
The previous interface of skygw_logmanager_init was conceptually broken. With -o you could specify that logging should be done to stdout. However, even if you did that, the log manager still checked that the logging directory could be accessed. Unless it had been specified using -j <path> the default was /var/log/maxscale. That is, unless the program calling skygw_logmanager_init was invoked by a user that had write access to /var/log/maxscale, there would be a complaint even if nothing was ever written to that directory. In practice this meant that even if -o was used you had to provide a -j with a path that surely is writeable (e.g. "/tmp"). This has now been changed so that you explicitly must provide the log directory and the flags -j and -o are removed. bool skygw_logmanager_init(const char* logdir, int argc, char* argv[]); If /logdir/ is provided then logged messages are written to a log file in that directory. If /logdir/ is NULL then messages are logged to stdout and no checks for access to any directory is not made.
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.