From 0ab07579071c5b53563d1c89efd0b54ef7436f7d Mon Sep 17 00:00:00 2001
From: Levi Quinn <Levence@gmail.com>
Date: Thu, 1 Sep 2022 10:33:12 +1000
Subject: [PATCH] fix(issue): ensure that most recent replica_host is treated
 as master for #3962

---
 lib/MySQL_Monitor.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/MySQL_Monitor.cpp b/lib/MySQL_Monitor.cpp
index ab8f8d875..3a062f2da 100644
--- 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, "