[
https://issues.apache.org/jira/browse/CASSANDRA-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986540#action_12986540
]
Jonathan Ellis commented on CASSANDRA-2052:
-------------------------------------------
As discussed in CASSANDRA-919 and CASSANDRA-959, I think this is the Wrong Fix.
Timeouts indicate an overload scenario, so retrying might get you your results
eventually, but it's more likely to perpetuate the over-capacity problem,
causing more timeouts, causing more retries, ...
> Add configurable retry count to Hadoop code
> -------------------------------------------
>
> Key: CASSANDRA-2052
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2052
> Project: Cassandra
> Issue Type: Improvement
> Components: Hadoop
> Affects Versions: 0.6.9, 0.7.0
> Reporter: Jeremy Hanna
>
> The Hadoop integration code doesn't do a retry if it times out. Often people
> have to tune the batch size and the rpc timeout in order to get it to work.
> We should probably have a configurable timeout in there (credit to Jairam -
> http://www.mail-archive.com/user@cassandra.apache.org/msg08938.html) so that
> it doesn't just fail the job with a timeout exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
