[MXS-2367] No warning about missing REPLICATION SLAVE Created: 2019-03-06  Updated: 2020-08-25  Resolved: 2019-06-19

Status: Closed
Project: MariaDB MaxScale
Component/s: mariadbmon
Affects Version/s: 2.3.5
Fix Version/s: 2.3.9

Type: Bug Priority: Major
Reporter: markus makela Assignee: Esa Korhonen
Resolution: Fixed Votes: 0
Labels: None

Sprint: MXS-SPRINT-83, MXS-SPRINT-84

 Description   

If the replication_user doesn't have the REPLICATION SLAVE grant, the failover will work but starting the slaves will fail. A warning that mentions the lack of correct grants would help avoid these sorts of problems in the future.



 Comments   
Comment by Esa Korhonen [ 2019-06-05 ]

Users should generally use the same username for the "replication_user" as is already used for replication. As such, this should be already visible by replication being broken before attempting failover/switchover.

Comment by Esa Korhonen [ 2019-06-17 ]

Added code which prints the slave connection errors if the slave doesn't connect within time limit.

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