You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "sankalp kohli (JIRA)" <ji...@apache.org> on 2016/07/01 03:04:11 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=15358301#comment-15358301 ] 

sankalp kohli commented on CASSANDRA-12075:
-------------------------------------------

Sure we can document it. The only thing is that if we add an exception which we dont want good drivers to not retry, we also need to patch the driver right away for this to work. Example: Say we add an exception which we dont want driver to retry. Now we will need to do changes in driver code and deploy this to the application. Normally client deployment are less infrequent as it is not in the control of the team running Cassandra. 



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