Hi Signoz team, I'm experiencing intermittent errors in my ClickHouse container. The error message I'm receiving is as follows:

{"date_time":"1742188589.608187","thread_name":"TCPServerConnection ([#1])","thread_id":"46","level":"Error","query_id":"","logger_name":"ServerErrorHandler","message":"Poco::Exception. Code: 1000, e.code() = 32, I/O error: Broken pipe, Stack trace (when copying this message, always include the lines below):\n\n0. Poco::Net::SocketImpl::error(int, String const&) @ 0x00000000153a1b5f in /usr/bin/clickhouse\n1. Poco::Net::SocketImpl::sendBytes(void const*, int, int) @ 0x00000000153a2bbd in /usr/bin/clickhouse\n2. Poco::Net::StreamSocketImpl::sendBytes(void const*, int, int) @ 0x00000000153a5296 in /usr/bin/clickhouse\n3. Poco::Net::HTTPSession::write(char const*, long) @ 0x00000000153908b3 in /usr/bin/clickhouse\n4. Poco::Net::HTTPHeaderIOS::~HTTPHeaderIOS() @ 0x000000001538bbdb in /usr/bin/clickhouse\n5. Poco::Net::HTTPHeaderOutputStream::~HTTPHeaderOutputStream() @ 0x000000001538bf1f in /usr/bin/clickhouse\n6. DB::HTTPServerResponse::send() @ 0x0000000012942988 in /usr/bin/clickhouse\n7. DB::HTTPServerConnection::sendErrorResponse(Poco::Net::HTTPServerSession&, Poco::Net::HTTPResponse::HTTPStatus) @ 0x000000001293ecda in /usr/bin/clickhouse\n8. DB::HTTPServerConnection::run() @ 0x000000001293e97b in /usr/bin/clickhouse\n9. Poco::Net::TCPServerConnection::start() @ 0x00000000153a5a72 in /usr/bin/clickhouse\n10. Poco::Net::TCPServerDispatcher::run() @ 0x00000000153a6871 in /usr/bin/clickhouse\n11. Poco::PooledThread::run() @ 0x000000001549f047 in /usr/bin/clickhouse\n12. Poco::ThreadImpl::runnableEntry(void*) @ 0x000000001549d67d in /usr/bin/clickhouse\n13. ? @ 0x000071476755c609\n14. ? @ 0x0000714767481353\n (version 24.1.2.5 (official build))","source_file":"src/Common/Exception.cpp; void DB::tryLogCurrentExceptionImpl(Poco::Logger *, const std::string &)","source_line":"222"}

I have deployed the latest version (v76.0) of self-hosted Signoz using Docker Swarm. My setup includes one manager and two worker nodes (t3.xlarge, 4 vCPUs and 16 GB RAM), and I have configured a high-availability setup with three ClickHouse containers running. Could someone help me understand and resolve this error? Thank you!

Hi Narayan, This should not affect your operations. Are you not able to use SigNoz?

I am able to use SigNoz and see data on the SigNoz frontend. While checking the logs of all containers, I found these errors in the ClickHouse container. Are these logs normal?

Yess you can ignore this!