[
https://issues.apache.org/jira/browse/CASSANDRA-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-2819:
--------------------------------------
Attachment: 2819-v9.txt
I was thinking about this wrong... we actually want to set up the EM with
min(timeouts); as long as most of the operations are reasonably close to that,
we'll be fine. Which, since the main outlier for us are truncates which are
relatively rare, matches our requirements nicely.
v9 attached with that added.
> 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.2
>
> Attachments: 2819-v4.txt, 2819-v5-rebased.txt, 2819-v8.txt,
> 2819-v9.txt, c2819-v6, c2819-v7, 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
