[
https://issues.apache.org/jira/browse/CASSANDRA-12075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15353915#comment-15353915
]
sankalp kohli commented on CASSANDRA-12075:
-------------------------------------------
If you get a Unavailable from co-ordinator, you should retry it on another host
since this co-ordinator could be doing a long GC pause.
We will be adding some more exceptions like throttles, too many tombstones
exception and it will be good for driver to know whether it should be retying
on a particular exception. This will be a better approach than driver special
casing which exception to retry or not. Also with different implementations of
the driver, it will be a lot helpful to not have this decision left to the
client.
> 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)
