Downgrade no heartbeat scenario logging

When RMQ connection is disconnected due to no heartbeat, there are multiple ERROR traces that are logged. This reduces the noise. Signed-off-by: Will <[email protected]>
bloomberg · Jan 17, 2024 · ce7c0d8 · ce7c0d8
1 parent 68bcaa8
commit ce7c0d8
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/src/rmq/rmqamqp/rmqamqp_heartbeatmanagerimpl.cpp b/src/rmq/rmqamqp/rmqamqp_heartbeatmanagerimpl.cpp
@@ -94,8 +94,8 @@ void HeartbeatManagerImpl::handleTick(rmqio::Timer::InterruptReason reason)
  d_ticksUntilHeartBeat = d_totalTicksUntilHeartBeat;
  }
  if (d_ticksUntilDisconnect == 0) {
- BALL_LOG_ERROR << "Received no heartbeats for " << d_timeoutSeconds
-  << "seconds. Triggering connection termination";
+ BALL_LOG_WARN << "Received no heartbeats for " << d_timeoutSeconds
+ << "seconds. Triggering connection termination";
  d_killConnection();
  d_ticksUntilDisconnect = d_totalTicksUntilDisconnect;
  }