[
https://issues.apache.org/jira/browse/CASSANDRA-12075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355864#comment-15355864
]
sankalp kohli commented on CASSANDRA-12075:
-------------------------------------------
By driver you mean Java Driver, Python driver, etc and by client you mean
application code talking to C* right?
Say we send out TombstoneOverwhelmingException to driver, it should definitely
not retry on its own no matter what retry policy the client code provide. Now
we cannot stop client code from sending the same request again.
Same example can be made with some other type of throttles as well. I agree
that other examples are recommendations but these 2 are not.
I am fine closing this JIRA and making these part of exceptions which driver
can interpret and will not retry? What do you think
> 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)
