[jira] [Commented] (CASSANDRA-2819) Split rpc timeout for read and write ops

["Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org>]

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

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

bq. wanna modify the getRpcTimeout in DD so that it returns the max of the other get*RpcTimeout()?

I think we need to split it into getGenericRpcTimeout (getMiscellaneousRpcTimeout?) and getMaxRpcTimeout.

bq. Not a so elegant solution in this patch. It uses the corresponding get*RpcTimeout in different callbacks.

looks good to me.
                
> 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.1
>
>         Attachments: 2819-v4.txt, 2819-v5-rebased.txt, c2819-v6, c2819.patch, 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira