cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stu Hood (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (CASSANDRA-2858) make request dropping more accurate
Date Thu, 28 Jul 2011 18:34:09 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072473#comment-13072473
] 

Stu Hood edited comment on CASSANDRA-2858 at 7/28/11 6:32 PM:
--------------------------------------------------------------

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

      was (Author: stuhood):
    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

        

Mime
View raw message