You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Josh McKenzie (Jira)" <ji...@apache.org> on 2020/01/02 16:59:00 UTC
[jira] [Assigned] (CASSANDRA-14520) ClosedChannelException handled
as FSError
[ https://issues.apache.org/jira/browse/CASSANDRA-14520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh McKenzie reassigned CASSANDRA-14520:
-----------------------------------------
Assignee: (was: Jason Brown)
> ClosedChannelException handled as FSError
> -----------------------------------------
>
> Key: CASSANDRA-14520
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14520
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Streaming and Messaging
> Reporter: Blake Eggleston
> Priority: Urgent
> Fix For: 4.0
>
>
> After the messaging service netty refactor, I’ve seen a few instances where a closed socket causes a ClosedChannelException (an IOException subclass) to be thrown. The exception is caught by ChannelProxy, interpreted as a disk error, and is then re-thrown as an FSError, causing the node to be shutdown.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org