From e0118c1378a6549fe4338033a5cff0597b3019cd Mon Sep 17 00:00:00 2001 From: Leandro Pacheco Date: Mon, 11 Feb 2019 18:22:29 +0100 Subject: [PATCH] removing assertion about current thread in next_fragment next_fragment is called outside the scope of a high_priority_switch, and we may be in a different thread context then the streaming applier was created in --- include/wsrep/client_state.hpp | 1 - 1 file changed, 1 deletion(-) diff --git a/include/wsrep/client_state.hpp b/include/wsrep/client_state.hpp index 6fad7eb..726fd22 100644 --- a/include/wsrep/client_state.hpp +++ b/include/wsrep/client_state.hpp @@ -439,7 +439,6 @@ namespace wsrep int next_fragment(const wsrep::ws_meta& meta) { wsrep::unique_lock lock(mutex_); - assert(current_thread_id_ == wsrep::this_thread::get_id()); assert(mode_ == m_high_priority); return transaction_.next_fragment(meta); }