[
https://issues.apache.org/jira/browse/CASSANDRA-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032823#comment-13032823
]
Stu Hood edited comment on CASSANDRA-2644 at 5/13/11 4:44 AM:
--------------------------------------------------------------
Good point. But there are still cases that retries will recover from...
flapping/down nodes, etc.
IMO, we should fix the performance issue independently (opened CASSANDRA-2645),
and consider retrying to be a best practice that should spread to more places
in the codebase.
was (Author: stuhood):
Good point.
> Make bootstrap retry
> --------------------
>
> Key: CASSANDRA-2644
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2644
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.8.0 beta 2
> Reporter: Chris Goffinet
> Assignee: Chris Goffinet
> Fix For: 0.8.1
>
> Attachments:
> 0001-Make-ExpiringMap-have-objects-with-specific-timeouts.patch,
> 0002-Make-bootstrap-retry-and-increment-timeout-for-every.patch
>
>
> We ran into a situation where we had rpc_timeout set to 1 second, and the
> node needing to compute the token took over a second (1.6 seconds). The
> bootstrapping node hangs forever without getting a token because the expiring
> map removes it before the reply comes back.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
