[
https://issues.apache.org/jira/browse/CASSANDRA-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Goffinet updated CASSANDRA-911:
-------------------------------------
Attachment: 0001-CASSANDRA-911-fixed-incorrect-timeout-calculation.patch
> QuorumResponseHandler sets timeout incorrectly
> ----------------------------------------------
>
> Key: CASSANDRA-911
> URL: https://issues.apache.org/jira/browse/CASSANDRA-911
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.6
> Reporter: Chris Goffinet
> Assignee: Chris Goffinet
> Priority: Minor
> Fix For: 0.6
>
> Attachments:
> 0001-CASSANDRA-911-fixed-incorrect-timeout-calculation.patch
>
>
> We noticed that the timeout calculation seems wrong:
> long timeout = System.currentTimeMillis() - startTime +
> DatabaseDescriptor.getRpcTimeout();
> Lets propose that 3 seconds elapse (currentTime - startTime). It will take
> that value and add the default RpcTimeout (5 seconds) making the timeout 8
> seconds.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
