[MXS-118] Two monitors loaded at the same time result into not working installation Created: 2015-04-24  Updated: 2015-06-17  Resolved: 2015-05-04

Status: Closed
Project: MariaDB MaxScale
Component/s: Documentation, galeramon, mariadbmon
Affects Version/s: None
Fix Version/s: 1.1.1

Type: Bug Priority: Minor
Reporter: Michaël de groot Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None


 Description   

When two monitors are loaded the MaxScale installation the MaxScale does not accept any queries. The clients get ERROR 1045, failed to create a new session.

The documentation is slightly off on this point in the configuration guide: https://github.com/mariadb-corporation/MaxScale/blob/master/Documentation/Getting-Started/Configuration-Guide.md#monitor
As they are in 1 code block the mistake can be made to copy/paste the whole of it.

I don't know if you consider this a bug or user error (why would the async replication need to be monitored on a galera cluster?) but I thought to report it as it caused some confiusion.

If the issue is related to having any 2 monitors I think it should be fixed as you may want to monitor a cluster with two different plugins.



 Comments   
Comment by markus makela [ 2015-04-30 ]

Updated documentation with clearer separation of the two monitors and an added warning about multiple monitors monitoring the same servers.

Comment by markus makela [ 2015-05-04 ]

Currently MaxScale does not support multiple monitors monitoring the same servers so I'll resolve this as a documentation bug.

Comment by Timofey Turenko [ 2015-05-05 ]

it is better to put at least warning to log file

Comment by markus makela [ 2015-05-05 ]

Added a warning to the error log if more than one monitor is monitoring a server.

Comment by Timofey Turenko [ 2015-05-12 ]

mxs118 test is added (https://github.com/mariadb-corporation/maxscale-system-test/blob/master/mxs118.cpp)

Generated at Thu Feb 08 03:56:55 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.