Hello,
I'm having an issue with the gracefull master takeover (automatic start replication mode) with Orchestrator.
My topology is made of 3 mysql servers, 1 master, 2 slaves, with MariaDB 10.5.15 : testmysql1/2/3.
Let's say testmysql1 is the master.
When i ask for a gracefull master takeover auto in order to set testmysql2 as master (with /usr/local/orchestrator/orchestrator -c graceful-master-takeover-auto -alias MyAlias -d testmysql2.mydomain:3306 ), everything goes fine :
(I'm still getting an error in the CLI ERROR GracefulMasterTakeover: sanity problem. Demoted master's coordinates changed from mysql-bin.000018:32587961 to mysql-bin.000018:32697914 while supposed to have been frozen but replication is fine).
But when i put back testmysql1 as master (so /usr/local/orchestrator/orchestrator -c graceful-master-takeover-auto -alias MyAlias -d testmysql1.mydomain:3306), i don't have any error in the CLI, but in the webui, the two new slaves servers show this error :
And indeed when i run a SHOW SLAVE STATUS \G; on my slaves servers, Slave SQL is not running and last error is :
Could not execute Delete_rows_v1 event on table orchestrator.cluster_alias; Can't find record in 'cluster_alias', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log mysql-bin.000018, end_log_pos 33779915
I don't know why, but table database_instance_maintenance in orchestrator database is empty on the newly promoted master server (testmysql1).
Then i just click on "Skip query" button and then replication starts again...
I don't really know why i've got this error...
Here is my configuration :
Hello, I'm having an issue with the gracefull master takeover (automatic start replication mode) with Orchestrator. My topology is made of 3 mysql servers, 1 master, 2 slaves, with MariaDB 10.5.15 : testmysql1/2/3. Let's say testmysql1 is the master. When i ask for a gracefull master takeover auto in order to set testmysql2 as master (with
/usr/local/orchestrator/orchestrator -c graceful-master-takeover-auto -alias MyAlias -d testmysql2.mydomain:3306
), everything goes fine : (I'm still getting an error in the CLIERROR GracefulMasterTakeover: sanity problem. Demoted master's coordinates changed from mysql-bin.000018:32587961 to mysql-bin.000018:32697914 while supposed to have been frozen
but replication is fine).But when i put back testmysql1 as master (so
/usr/local/orchestrator/orchestrator -c graceful-master-takeover-auto -alias MyAlias -d testmysql1.mydomain:3306
), i don't have any error in the CLI, but in the webui, the two new slaves servers show this error : And indeed when i run aSHOW SLAVE STATUS \G;
on my slaves servers, Slave SQL is not running and last error is :Could not execute Delete_rows_v1 event on table orchestrator.cluster_alias; Can't find record in 'cluster_alias', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log mysql-bin.000018, end_log_pos 33779915
I don't know why, but table database_instance_maintenance in orchestrator database is empty on the newly promoted master server (testmysql1). Then i just click on "Skip query" button and then replication starts again...I don't really know why i've got this error... Here is my configuration :
My orchestrator.conf.json :
Any idea of what i could've missed ? Or misconfigured ? Thanks a lot, i really appreciate Orchestrator, very usefull for my needs :+1: