You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2013/10/02 17:16:42 UTC

[jira] [Commented] (CASSANDRA-6133) Tracing should deal with write failure

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

Aleksey Yeschenko commented on CASSANDRA-6133:
----------------------------------------------

Hmm. Shall we ever get UAE when writing with CL.ANY? I don't think so. Same re WTE, once CASSANDRA-6132 is resolved.

Only OE should be possible. I'd replace all those catch-es with a single catch (REE) with assert e instanseof OE and the log warning for 'too many nodes are overloaded to save trace events'.

Other than that +1.

> Tracing should deal with write failure
> --------------------------------------
>
>                 Key: CASSANDRA-6133
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6133
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core, Tools
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Trivial
>             Fix For: 1.2.11, 2.0.2
>
>         Attachments: 6133.txt
>
>




--
This message was sent by Atlassian JIRA
(v6.1#6144)