cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-9419) CqlRecordWriter does not adequately determine if driver failed to connect due to interrupt
Date Tue, 19 May 2015 11:30:59 GMT

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

Sam Tunnicliffe updated CASSANDRA-9419:
---------------------------------------
    Reviewer: Sam Tunnicliffe  (was: Aleksey Yeschenko)

> 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 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)

Mime
View raw message