From 1ddcbc9ae1bfbd2083a93341527f709fbb4ab725 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Markus=20M=C3=A4kel=C3=A4?= Date: Thu, 18 Jul 2019 17:58:22 +0300 Subject: [PATCH] Log error message on slave session command failure If the slave's response differs from the master and the slave sent an error packet, log the contents of the error. This should make it obvious as to what caused the failure. --- server/modules/routing/readwritesplit/rwsplit_session_cmd.cc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/server/modules/routing/readwritesplit/rwsplit_session_cmd.cc b/server/modules/routing/readwritesplit/rwsplit_session_cmd.cc index 762cd10ef..0f13a18ab 100644 --- a/server/modules/routing/readwritesplit/rwsplit_session_cmd.cc +++ b/server/modules/routing/readwritesplit/rwsplit_session_cmd.cc @@ -149,8 +149,8 @@ void RWSplitSession::process_sescmd_response(SRWBackend& backend, GWBUF** ppPack { if (cmd == MYSQL_REPLY_ERR && m_sescmd_responses[id] != MYSQL_REPLY_ERR) { - MXS_INFO("Session command failed on slave '%s': %s", - backend->name(), extract_error(*ppPacket).c_str()); + MXS_WARNING("Session command failed on slave '%s': %s", + backend->name(), extract_error(*ppPacket).c_str()); } discard_if_response_differs(backend, m_sescmd_responses[id], cmd, sescmd);