Skip to content

Commit fd94c35

Browse files
author
Richard Gildea
committed
Lower failed connection log level to warning
Since the failed connection is caught and handled, i.e. we will subsequently reconnect, it probably makes sense to only emit a warning rather than an error. This may occur e.g. if a cluster job running a wrapper gets suspended. On job resumption we encounter some form of failed connection error (typically StreamLostError/ConnectionResetError or sometimes AMQPHeartbeatTimeout).
1 parent 23afa20 commit fd94c35

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

src/workflows/transport/pika_transport.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1482,7 +1482,7 @@ def _run(self):
14821482
if connection_counter == 0:
14831483
logger.error(f"Initial connection failed: {e!r}")
14841484
break
1485-
logger.error(f"Connection {connection_counter} failed: {e!r}")
1485+
logger.warning(f"Connection {connection_counter} failed: {e!r}")
14861486
except BaseException as e:
14871487
logger.error(f"Connection failed for unknown reason: {e!r}")
14881488
self._exc_info = sys.exc_info()

0 commit comments

Comments
 (0)