[MXS-3934] Linking a service at runtime to an xpandmon doesn't work Created: 2022-01-04  Updated: 2022-01-12  Resolved: 2022-01-12

Status: Closed
Project: MariaDB MaxScale
Component/s: xpandmon
Affects Version/s: 2.5.17, 6.2.0
Fix Version/s: 2.5.18, 6.2.1

Type: Bug Priority: Major
Reporter: markus makela Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None


 Description   

When a service is linked to a xpandmon monitor which has already discovered all the nodes, the existing servers (dynamic nodes created by xpandmon) don't seem to be added to the service. This causes the service to have no servers in it.

With a monitor like this in the configuration:

[Xpand-Monitor]
type=monitor
module=xpandmon
user=user
password=pw
servers=bootstrap
monitor_interval=2000

and with a service created like this:

maxctrl create service Xpand-Service readwritesplit user=user password=password
maxctrl link service Xpand-Service Xpand-Monitor
maxctrl create listener Xpand-Service Xpand-Listener 4006

If xpandmon has already discovered all nodes, the servers won't be added to the service and as a result, it behaves as if it had no nodes. A workaround to this is to unlink and link the bootstrap server to the monitor.


Generated at Thu Feb 08 04:25:00 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.