[
https://issues.apache.org/jira/browse/CASSANDRA-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032871#comment-13032871
]
Sylvain Lebresne commented on CASSANDRA-2644:
---------------------------------------------
Not fully related to the discussion here but streaming is another part of
bootstrap so I'll mention that CASSANDRA-2433 introduces some mechanism to
handle unrecoverable failures during streaming (that is, streaming already
retry on errors but 1) it retries indefinitely while the CASSANDRA-2433
introduce a max retry and 2) it doesn't detect the other end being dead).
Anyway, just referencing the ticket so that if this ticket becomes "make
bootstrap handle failures better", we don't duplicate efforts.
> 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
