[
https://issues.apache.org/jira/browse/CASSANDRA-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-2819:
--------------------------------------
Attachment: 2819-v4.txt
v4 attached (against trunk), with compilation fixes.
Looks like it needs another check for uses of DD.getRpcTimeout. Here are some
suspicious ones:
- MS.timeoutReporter
- ReadCallback
- RepairCallback
- StorageProxy.DroppableRunnable
> 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: 2819-v4.txt, 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
