[MXS-3752] Automatic rejoin failed Created: 2021-09-01  Updated: 2021-09-02  Resolved: 2021-09-02

Status: Closed
Project: MariaDB MaxScale
Component/s: failover
Affects Version/s: 6.1.0
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Christian Angelo Sulit Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: None


 Description   

[mariadbmon] Automatic rejoin was not attempted on server 'server1' even though it is a valid candidate. Will keep retrying with this message suppressed for all servers. Errors:
gtid_current_pos of 'server1' (0-1-19) is incompatible with gtid_binlog_pos of 'server2' (0-2-6).

Master DB (10.6) replication config:
server-id=1
gtid_strict_mode=1
log-slave-updates=ON
log-bin = /var/lib/mysql/bin-mariadb.log
expire-logs-days=8
sync_binlog = 1
slave_compressed_protocol
transaction-isolation = READ-COMMITTED
binlog_format = row

Maxscale (6-1-1-GA) config:
monitor_interval=100
auto_failover=true
auto_rejoin=true
enforce_read_only_slaves=1
backend_connect_timeout=2
backend_read_timeout=2
backend_write_timeout=2
master_failure_timeout=2
verify_master_failure=true
failcount=2
switchover_timeout=20
failover_timeout=20



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

Looks like server1 has an incompatible GTID position as it is ahead of server2. This seems like expected behavior since if the node did rejoin it would have diverged from the rest of the cluster.

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