You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2012/09/03 19:48:07 UTC
[jira] [Updated] (CASSANDRA-2858) make request dropping more
accurate
[ https://issues.apache.org/jira/browse/CASSANDRA-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-2858:
--------------------------------------
Attachment: 2858.txt
bq. The ExpiringMap of callbacks on the client side always waits until the RPC timeout to expire messages
Not so, ResponseVerbHandler calls removeRegisteredCallback.
bq. A client thread calling get() on a callback has a timeout independent from the timeout for the Callback in the ExpiringMap
That would be nice to clean up in a separate ticket.
bq. The originally mentioned issue of not having an accurate timeout on the server side
This is the most important part to address. Patch attached.
> make request dropping more accurate
> -----------------------------------
>
> Key: CASSANDRA-2858
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2858
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Ryan King
> Assignee: Melvin Wang
> Priority: Minor
> Fix For: 1.2.0 beta 1
>
> Attachments: 2858.txt
>
>
> Based on the discussion in CASSANDRA-2819, we can make the bookkeeping for request times more accurate.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira