[MXS-3000] Not all global parameters are serialized Created: 2020-05-20  Updated: 2020-05-25  Resolved: 2020-05-25

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 2.4.9
Fix Version/s: 2.4.10

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

Issue Links:
Duplicate
is duplicated by MXS-3001 maxctrl does not persists dynamic cha... Closed

 Description   

The following the core parameters that could be modified at runtime were not serialized to disk.

  • admin_log_auth_failures
  • query_classifier_cache_size
  • writeq_high_water
  • writeq_low_water
  • ms_timestamp
  • skip_permission_checks
  • query_retries
  • query_retry_timeout
  • retain_last_statements
  • dump_last_statements
  • max_auth_errors_until_block
  • session_trace

 Comments   
Comment by Massimo [ 2020-05-21 ]

hi

on the 2.4. documentation is reporting this:
alter maxscale¶
Usage: alter maxscale <key> <value> ...

To display the MaxScale parameters, execute show maxscale. The following list of parameters can be altered at runtime:

[ "auth_connect_timeout", "auth_read_timeout", "auth_write_timeout", "admin_auth", "admin_log_auth_failures", "passive", "ms_timestamp", "skip_permission_checks", "query_retries", "query_retry_timeout", "retain_last_statements", "dump_last_statements" ]

the list of parameters isnt up to date, as we have seen in 2.4.8 for writeq_high_water and writeq_low_water. Please be sure the list of parameter that can be change runtime is uptodate on the doc as well

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