fix(issue): ensure that most recent replica_host is treated as master for #3962

4 years ago · 0ab0757907
parent 3a590ba481
commit 0ab0757907
1 changed files with 1 additions and 1 deletions
--- a/lib/MySQL_Monitor.cpp
+++ b/lib/MySQL_Monitor.cpp
@ -4466,7 +4466,7 @@ void * monitor_AWS_Aurora_thread_HG(void *arg) {
 			"SELECT SERVER_ID,"
 			"IF("
 				"SESSION_ID = 'MASTER_SESSION_ID' AND "
-				"SERVER_ID <> (SELECT SERVER_ID FROM INFORMATION_SCHEMA.REPLICA_HOST_STATUS WHERE SESSION_ID = 'MASTER_SESSION_ID' ORDER BY LAST_UPDATE_TIMESTAMP ASC LIMIT 1), "
+				"SERVER_ID <> (SELECT SERVER_ID FROM INFORMATION_SCHEMA.REPLICA_HOST_STATUS WHERE SESSION_ID = 'MASTER_SESSION_ID' ORDER BY LAST_UPDATE_TIMESTAMP DESC LIMIT 1), "
 				"'probably_former_MASTER_SESSION_ID', SESSION_ID"
 			") SESSION_ID, " // it seems that during a failover, the old writer can keep MASTER_SESSION_ID because not updated
 			"LAST_UPDATE_TIMESTAMP, "