[MXS-4745] Update example configuration Created: 2023-09-06  Updated: 2023-09-22  Resolved: 2023-09-22

Status: Closed
Project: MariaDB MaxScale
Component/s: Documentation
Affects Version/s: None
Fix Version/s: 6.4.11, 22.08.9, 23.02.5, 23.08.2

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

Issue Links:
Relates
relates to MXS-4744 Add optional auto-failover configurat... Closed
Sprint: MXS-SPRINT-191

 Description   

The example configuration is functional but somewhat minimal. It also offers no help in figuring out which commonly used features should be enabled or not.

For servers, the proxy_protocol parameter should be mentioned as a way to reduce the amount of user account management that has to be done when the accounts do not use wildcards that cover both the client IP and the MaxScale IP.

For readwritesplit, a commented out section with transaction_replay and some of the parameters that can be enabled with it would be a way to improve the HA aspects of it. Another comment should explains how causal_reads solves most problems with single database applications that do writes with autocommit and then read the data that was just written.

The mariadbmon section is covered by MXS-4744.

The global configuration could have a section for some of the newer parameters like auto_tune that make the configuration of the cluster and its limits a simpler task.


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