[
https://issues.apache.org/jira/browse/CASSANDRA-20072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-20072:
-----------------------------------------
Fix Version/s: 4.0.15
4.1.8
5.0.3
5.1-alpha1
(was: 5.x)
(was: 4.0.x)
(was: 4.1.x)
(was: 5.0.x)
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
bq. I do not think that adding there no-spam logger is a good idea for now.
I agree it's a bit premature for that. Thanks for the review, this is
committed.
> Log client address when detecting unknown exception in client networking
> -------------------------------------------------------------------------
>
> Key: CASSANDRA-20072
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20072
> Project: Cassandra
> Issue Type: Bug
> Components: Observability/Logging
> Reporter: Mohammad Aburadeh
> Assignee: Mohammad Aburadeh
> Priority: Urgent
> Fix For: 4.0.15, 4.1.8, 5.0.3, 5.1-alpha1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> We are getting hundreds of the below warnings in Cassandra logs:
> {code:java}
> WARN [epollEventLoopGroup-5-7] 2024-11-10 00:26:24,296
> ExceptionHandlers.java:139 - Unknown exception in client networking
> io.netty.channel.StacklessClosedChannelException: null
> at io.netty.channel.AbstractChannel.close(ChannelPromise)(Unknown
> Source)
> {code}
> This means the client dropped the connection abruptly or abnormally. The
> issue could be a network or application issue on the client side.
> Since there could be many client servers, Cassandra must log the client IP
> and the port so we can check what's the problem with that server.
> I'll attached the fix for this small change.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
