[MXS-3424] retain_last_statements cannot be disabled at runtime Created: 2021-03-02  Updated: 2021-03-25  Resolved: 2021-03-02

Status: Closed
Project: MariaDB MaxScale
Component/s: maxctrl
Affects Version/s: 2.4.16
Fix Version/s: 2.4.17

Type: Bug Priority: Major
Reporter: Allen Lee (Inactive) Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None


 Description   

This is the same issue in v2.4.16 as MXS-2711. However, I was able to set it 0 in config file and restart maxscale.

[root@node1 maxscale.cnf.d]# maxctrl alter maxscale retain_last_statements 0
 
Error: Invalid value



 Comments   
Comment by markus makela [ 2021-03-02 ]

Tested this with 2.5 and it seems to work there.

This seems like it might be an error reported by MaxCtrl rather than MaxScale. It does a rudimentary check that no arguments that are given are empty or null values and if they are, it reports this error.

Comment by markus makela [ 2021-03-02 ]

Turns out that this was a case of maxctrl not using strict equality to compare the values. This means that the integer value 0 compared equal to an empty string which caused maxctrl to report that error.

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