search

openark / orchestrator

MySQL replication topology management and HA
Apache License 2.0
5.61k stars 927 forks source link

orchestrator errant GTID only in GUI but not in CLI #885

Closed hellracer closed 5 years ago

hellracer commented 5 years ago

Hi,

Could someone shed some light as to why the GUI says i have an errant GTID whilst the CLI suggest that everything is working as it should or do i miss something?

root@ProxySQL:~/orchestrator# orchestrator -c locate-gtid-errant -i db01
2019-05-12 15:42:49 DEBUG Hostname unresolved yet: db01
2019-05-12 15:42:49 DEBUG Cache hostname resolve db01 as db01
2019-05-12 15:42:49 DEBUG Connected to orchestrator backend: orchestrator:?@tcp(127.0.0.1:3306)/orchestrator?timeout=1s
2019-05-12 15:42:49 DEBUG Orchestrator pool SetMaxOpenConns: 128
2019-05-12 15:42:49 DEBUG Initializing orchestrator
2019-05-12 15:42:49 DEBUG Migrating database schema
2019-05-12 15:42:49 DEBUG Hostname unresolved yet: 192.168.137.9
2019-05-12 15:42:49 DEBUG Cache hostname resolve 192.168.137.9 as 192.168.137.9
2019-05-12 15:42:49 DEBUG Hostname unresolved yet: 192.168.137.9
2019-05-12 15:42:49 DEBUG Cache hostname resolve 192.168.137.9 as 192.168.137.9
2019-05-12 15:42:49 DEBUG Hostname unresolved yet: 192.168.142.22
2019-05-12 15:42:49 DEBUG Cache hostname resolve 192.168.142.22 as 192.168.142.22
2019-05-12 15:42:49 ERROR locate-errant-gtid: no errant-gtid on DB01:3306
2019-05-12 15:42:49 FATAL 2019-05-12 15:42:49 ERROR locate-errant-gtid: no errant-gtid on DB01:3306```

But in GUI

Screen Shot 2019-05-12 at 3 41 04 PM


and also injecting empty transaction won't fix the errant GTID.

orchestrator 3.0.14 (commit ce78f28e7c5bdf7a821573444d6cada050e61cfa)
hellracer commented 5 years ago

does #707 implementation should fix the errant GTID in the gui?, when i click the FIX button and confirmed injecting empty transaction in the dialog, the spinner in the gui just keep on spinning without any confirmation if it was indeed inject the transaction in the master.

hellracer commented 5 years ago

I think i haven't wait long enough for the fix to fully apply on the master, but still the question remains why the GUI and the CLI mismatch in behaviour.

hellracer commented 5 years ago

Please close this, the issue here is the cache in the GUI, when I click FIX button and refresh instance the GUI and CLI is now in sync...

shlomi-noach commented 5 years ago

Glad it worked