[jira] [Comment Edited] (CASSANDRA-9419) CqlRecordWriter does not adequately determine if driver failed to connect due to interrupt

["Philip Thompson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-9419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14551067#comment-14551067 ] 

Philip Thompson edited comment on CASSANDRA-9419 at 5/19/15 7:27 PM:
---------------------------------------------------------------------

New Patch is at https://github.com/apache/cassandra/compare/cassandra-2.2...ptnapoleon:cassandra-9419


was (Author: philipthompson):
New Patch is at https://github.com/apache/cassandra/compare/trunk...ptnapoleon:cassandra-9419

> CqlRecordWriter does not adequately determine if driver failed to connect due to interrupt
> ------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-9419
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9419
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Philip Thompson
>            Assignee: Philip Thompson
>             Fix For: 2.2.0 rc1
>
>         Attachments: 9419.txt
>
>
> Until https://datastax-oss.atlassian.net/browse/JAVA-769 is implemented, I have had to implement a workaround.
> Java's thread interrupt status flag can be cleared for any number of reasons. After discussion, I've changed to parsing the driver's DriverException to tell if we are safe to retry the failed connection.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)