[
https://issues.apache.org/jira/browse/CASSANDRA-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131256#comment-13131256
]
Melvin Wang commented on CASSANDRA-2819:
----------------------------------------
bq. Writes still use the old rpc_timeout
Changed to getWriteRpcTimeout()
bq. looks like most remaining uses of old rpc_timeout should really be
max(different timeouts)
wanna modify the getRpcTimeout in DD so that it returns the max of the other
get*RpcTimeout()?
bq. currently, expiring map checks callbacks for expiration every 1/2 of
default timeout. This means short timeouts could go much longer than desired,
before being cancelled. I see two options: go back to direct await(timeout) in
the callback/response handlers, or update EM to scan much more frequently
(which could burn a lot of CPU for a system with many outstanding callbacks)
Not a so elegant solution in this patch. It uses the corresponding
get*RpcTimeout in different callbacks.
> 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.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
