From 10de63f9b69a120762e0cedcb21c12a163c6b503 Mon Sep 17 00:00:00 2001
From: Marco Neumann <marco@crepererum.net>
Date: Wed, 3 Nov 2021 16:03:38 +0100
Subject: [PATCH] refactor: warn when we receive broken data from write buffer

We need to understand why this is the case and where broken data gets
stuck, because at the moment it seems that some Kafka hiccups can
poison the write buffer but it seems restarting IOx recovers the
situation.
---
 server/src/write_buffer.rs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/server/src/write_buffer.rs b/server/src/write_buffer.rs
index e3d58694b9..6562423f8f 100644
--- a/server/src/write_buffer.rs
+++ b/server/src/write_buffer.rs
@@ -142,7 +142,7 @@ async fn stream_in_sequenced_entries<'a>(
             Ok(db_write) => db_write,
             // skip over invalid data in the write buffer so recovery can succeed
             Err(e) => {
-                debug!(
+                warn!(
                     %e,
                     %db_name,
                     sequencer_id,