[MXS-2791] Special arguments are not passed to MaxScale's monitor script Created: 2019-12-09 Updated: 2020-08-25 Resolved: 2019-12-10 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Monitor |
| Affects Version/s: | 2.3.15, 2.4.4 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Geoff Montee (Inactive) | Assignee: | Johan Wikman |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||||||
| Description |
|
MaxScale allows users to set a script parameter for all monitors. When this parameter is set, MaxScale will execute the specified script whenever the cluster changes in some way. MaxScale is supposed to pass special arguments to the script, and these special arguments are supposed to contain information about the cluster change. https://mariadb.com/kb/en/mariadb-maxscale-24-common-monitor-parameters/#script Unfortunately, MaxScale does not currently pass the special arguments to the script at all. To test this, we can create a very simple script:
And then we can configure MaxScale to use the script:
When the cluster changes, MaxScale does execute the script, but we can see that no arguments are passed to it:
|
| Comments |
| Comment by Geoff Montee (Inactive) [ 2019-12-10 ] | ||||||||||
|
It looks like the problem is that the value provided to the script parameter needs to include the relevant arguments. For example, something like this works:
|