From d0fd65be577f3d808d3643a3c901e12c28bd1c86 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Markus=20M=C3=A4kel=C3=A4?= <markus.makela@mariadb.com>
Date: Tue, 10 Oct 2017 06:10:11 +0300
Subject: [PATCH] Fix unintentional fallthrough

When LEAST_BEHIND_MASTER routing criteria was used, the info level logging
function would fall through to the default case. In debug builds, this
would trigger a debug assertion.
---
 .../modules/routing/readwritesplit/rwsplit_select_backends.cc   | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/server/modules/routing/readwritesplit/rwsplit_select_backends.cc b/server/modules/routing/readwritesplit/rwsplit_select_backends.cc
index 80ef9b988..ef64b0480 100644
--- a/server/modules/routing/readwritesplit/rwsplit_select_backends.cc
+++ b/server/modules/routing/readwritesplit/rwsplit_select_backends.cc
@@ -231,6 +231,8 @@ static void log_server_connections(select_criteria_t criteria, const SRWBackendL
             MXS_INFO("replication lag : %d in \t[%s]:%d %s",
                      b->server->rlag, b->server->name,
                      b->server->port, STRSRVSTATUS(b->server));
+            break;
+
         default:
             ss_dassert(!true);
             break;