cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5426) Redesign repair messages
Date Mon, 03 Jun 2013 14:15:21 GMT

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

Yuki Morishita commented on CASSANDRA-5426:
-------------------------------------------

[~jasobrown] Actually, I think that try catch block is redundant. Streaming does not run on
the same thread as StreamingRepairTask does and exception should be handled at IStreamCallback's
onError method(which is empty in current 1.2).
I'm trying to overhaul streaming API for 2.0(CASSANDRA-5286) and it should have more fine
grained control over streaming.
                
> Redesign repair messages
> ------------------------
>
>                 Key: CASSANDRA-5426
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5426
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Yuki Morishita
>            Assignee: Yuki Morishita
>            Priority: Minor
>              Labels: repair
>             Fix For: 2.0
>
>
> Many people have been reporting 'repair hang' when something goes wrong.
> Two major causes of hang are 1) validation failure and 2) streaming failure.
> Currently, when those failures happen, the failed node would not respond back to the
repair initiator.
> The goal of this ticket is to redesign message flows around repair so that repair never
hang.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message