cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Doubleday (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-1862) StorageProxy throws an InvalidRequestException in readProtocol during bootstrap
Date Wed, 20 Apr 2011 15:42:05 GMT

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

Daniel Doubleday commented on CASSANDRA-1862:
---------------------------------------------

Don't know wether commenting a closed jira makes sense but I think that this made matters
worse because no bootstrapping is not distinguishable anymore.
I thought that UnavailableException would signal that a read cannot be served due to CL. And
a bootstrapping coordinator does not imply this right? 

> StorageProxy throws an InvalidRequestException in readProtocol during bootstrap
> -------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-1862
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1862
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 0.7.0 rc 2
>            Reporter: Nate McCall
>            Assignee: Nate McCall
>            Priority: Minor
>             Fix For: 0.7.0 rc 3
>
>         Attachments: 1862.txt, 1862_0.6.txt
>
>
> Though the error message provides details, IRE is supposed to signify poorly formed API
requests. In the context of a client request, an UnavailableException is more appropriate.
This would allow the client to take action like removing the node from its host list. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message