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 Fri, 01 Jul 2011 00:03:28 GMT

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

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

scratch my comments about the OTC part. It is not true. What I want is a checkpoint after
the server has processed the verb where we check if we are already timed out so that we won't
bother to use the network bandwidth to send back the response. I will move this logic into
MessagingService.

> 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: rpc-timeouts-per-verb.diff
>
>
> 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