[jira] [Comment Edited] (CASSANDRA-5009) RangeStreamer has no way to report failures, allowing bootstrap/move etc to complete without data

["Brandon Williams (JIRA)" <ji...@apache.org>]

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

Brandon Williams edited comment on CASSANDRA-5009 at 12/3/12 7:02 PM:
----------------------------------------------------------------------

Oops, exceptionMessage was a vestige from my initial attempt at backporting the 1.2 version before I discovered it was flawed too.

Updated patch removes that, moves the addAll call before the latch countdown, and initiates the set with a concurrent hash map.
                
      was (Author: brandon.williams):
    Oops, exceptionMessage was a vestige from my initial attempt at backporting the 1.2 version before I discovered it was flawed too.

Update patch removes, that, moves the addAll call before the latch countdown, and initiates the set with a concurrent hash map.
                  
> RangeStreamer has no way to report failures, allowing bootstrap/move etc to complete without data
> -------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-5009
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5009
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1.0
>            Reporter: Brandon Williams
>            Assignee: Brandon Williams
>            Priority: Critical
>             Fix For: 1.1.8
>
>         Attachments: 5009.txt, 5009-v2.txt
>
>
> It looks like we fixed this for 1.2 by having RS.fetch() throw, but in 1.1 it does not and there doesn't appear to be a way to detect an RS failure, which among other things will cause bootstrap to succeed even though it failed to fetch any data.

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