Monitor Plugin for Tungsten Connector

Tungsten Connector is installed on every database node of master - slave cluster. The application going through Tungsten connector should always attempt to go to primary host as master , if primary is not reachable then application should go to the secondary host. If primary host becomes available again, application should fallback to primary host. When MaxScale is connecting to backend database servers through Tungsten connector, Tungsten monitor in MaxScale needs to do the same - i.e. report primary host as master if it a reachable, other wise report secondary host as master.

The configuration needs to be similar to existing monitors:
[Tungsten Connector Monitor]
type=monitor
module=tungstenConMon
servers=primary-server1,secondary-server2,secondary-server3
user=dbmonitoruser
passwd=dbmonitorpwd
monitor_interval=8000
backend_connect_timeout=3

Every monitor interval, the monitor needs to

• reach to primary server(first one in servers list in monitor configuration), if it is reachable and responds to the query "SHOW STATUS LIKE 'UPTIME'" , then report the the primary node as master to the router
• Other wise try reaching the next secondary server defined in monitor configuration, do the same query "SHOW STATUS LIKE 'UPTIME'" . If this secondary server responds to the query, then report the the this secondary server node as master to the router, and so on