[MXS-4626] Use same parameter for readconnroute router and readwritespiter to define maximum acceptable replication lag. Created: 2023-05-26 Updated: 2023-08-09 Resolved: 2023-08-09 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | readwritesplit |
| Affects Version/s: | 23.02 |
| Fix Version/s: | 23.08.0 |
| Type: | Task | Priority: | Major |
| Reporter: | Maria M Pflaum | Assignee: | Johan Wikman |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Sprint: | MXS-SPRINT-188 | ||||||||
| Description |
|
Maxscale readconnroute router uses parameter max_replication_lag while readwritespliter uses max_slave_replication_lag. Customer requests a feature where readconnroute and readwritespliter both use the same parameter name. Additionally the readconnrouter documentation refers to both max_slave_replication_lag and max_replication_lag. https://mariadb.com/kb/en/mariadb-maxscale-2302-readconnroute/#max_replication_lag |
| Comments |
| Comment by Johan Wikman [ 2023-05-29 ] |
|
Reclassified as bug as there is no sensible reason why the parameter name should be different. |
| Comment by Johan Wikman [ 2023-08-09 ] |
|
Reclassified as a task as a non-optimal name does not as such affect the functionality. |