From 1e9325197a34a44cd728f9fdf5300531f0165ea1 Mon Sep 17 00:00:00 2001 From: Daniele Sciascia Date: Tue, 15 Jan 2019 10:57:39 +0100 Subject: [PATCH] Turn "Could not find applier context" into debug message Remove warning "Could not find applier context" when no applier context is found while applying rollback fragment. --- src/server_state.cpp | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/src/server_state.cpp b/src/server_state.cpp index 8c50f30..b90c7a9 100644 --- a/src/server_state.cpp +++ b/src/server_state.cpp @@ -160,12 +160,15 @@ static int apply_write_set(wsrep::server_state& server_state, ws_meta.server_id(), ws_meta.transaction_id())); if (sa == 0) { - // It is possible that rapid group membership changes - // may cause streaming transaction be rolled back before - // commit fragment comes in. Although this is a valid - // situation, log a warning if a sac cannot be found as - // it may be an indication of a bug too. - wsrep::log_warning() + // It is a known limitation that galera provider + // cannot always determine if certification test + // for interrupted transaction will pass or fail + // (see comments in transaction::certify_fragment()). + // As a consequence, unnecessary rollback fragments + // may be delivered here. The message below has + // been intentionally turned into a debug message, + // rather than warning. + wsrep::log_debug() << "Could not find applier context for " << ws_meta.server_id() << ": " << ws_meta.transaction_id();