You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Tyler Hobbs (JIRA)" <ji...@apache.org> on 2016/06/23 20:46:16 UTC

[jira] [Commented] (CASSANDRA-12075) Include whether or not the client should retry the request when throwing a RequestExecutionException

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

Tyler Hobbs commented on CASSANDRA-12075:
-----------------------------------------

Can you clarify what you intend the behavior to be?  What are we going to consider retryable vs not?

> Include whether or not the client should retry the request when throwing a RequestExecutionException
> ----------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-12075
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12075
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Geoffrey Yu
>            Assignee: Geoffrey Yu
>            Priority: Minor
>
> Some requests that result in an error should not be retried by the client. Right now if the client gets an error, it has no way of knowing whether or not it should retry. We can include an extra field in each {{RequestExecutionException}} that will indicate whether the client should retry, retry on a different host, or not retry at all.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)