[
https://issues.apache.org/jira/browse/CASSANDRA-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072473#comment-13072473
]
Stu Hood commented on CASSANDRA-2858:
-------------------------------------
There are a few issues here:
* The originally mentioned issue of not having an accurate timeout on the
server side
* Add a creation time on the client side? Set the remaining time immediately
before serialization?
* The ExpiringMap of callbacks on the client side always waits until the RPC
timeout to expire messages
* The Callback could eagerly expire itself from the map when it is is
satisfied
* A client thread calling get() on a callback has a timeout independent from
the timeout for the Callback in the ExpiringMap: they can become disconnected
* One way to solve that would be to change the IAsyncCallback interface to
be more like a Future, such that it is notified when it expires, and could kill
anyone blocking on get() with a TimeoutException
> 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
>
> Based on the discussion in
> https://issues.apache.org/jira/browse/CASSANDRA-2819, we can make the
> bookkeeping for request times more accurate.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
