cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-2819) Split rpc timeout for read and write ops
Date Sat, 30 Jul 2011 02:58:11 GMT

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

Jonathan Ellis commented on CASSANDRA-2819:
-------------------------------------------

Thanks, Melvin!

should we move MS.getMessageTimeout to an instance method of Message?  This would make per-Message
timeouts easier in the future as well.

Let's make the default values in Config 10s as well, to avoid surprising people who upgrade
but keep their old config file around.

Otherwise LGTM.

> 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: twttr-cassandra-0.8-counts-resync-rpc-rw-timeouts.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