[jira] [Issue Comment Deleted] (CASSANDRA-14520) ClosedChannelException handled as FSError

["Kevin Gallardo (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-14520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Gallardo updated CASSANDRA-14520:
---------------------------------------
    Comment: was deleted

(was: Discussed this with [~blerer] in details and it seems that the second {{ClosedByInterruptException}} appearing in the stacktrace was caused by the first exception. It is hard to track exactly how that was happening because of the large refactoring around streaming and other parts of the code since the ticket was opened.
It would be safer to keep the current behavior in the {{ChannelProxy}} which is to throw an Error in case of an IOException.
Will close the issue, if this issue happens again with the current state of the code we can have a better look and figure out if the {{ClosedByInterruptException}} is still problematic.)

> 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
>            Assignee: Kevin Gallardo
>            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