cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Melvin Wang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-2819) Split rpc timeout for read and write ops
Date Mon, 01 Aug 2011 21:04:49 GMT

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

Melvin Wang commented on CASSANDRA-2819:
----------------------------------------

In MS.timeoutReporter, we blindly add default rpc timeout as the latency. Since different
messages may have different timeout now, in ExpiringMap.CacheMonitor, probably we need to
pass the individual expiration time when we call apply().

> Split rpc timeout for read and write ops
> ----------------------------------------
>
>                 Key: CASSANDRA-2819
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2819
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Stu Hood
>            Assignee: Melvin Wang
>             Fix For: 1.0
>
>         Attachments: 2819-v4.txt, rpc-jira.patch
>
>
> Given the vastly different latency characteristics of reads and writes, it makes sense
for them to have independent rpc timeouts internally.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message