[
https://issues.apache.org/jira/browse/CASSANDRA-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Melvin Wang updated CASSANDRA-2819:
-----------------------------------
Attachment: c2819-v7
Please take another look. Following changes made
* CassandraServer.java, set the timeout when we schedule individual Rpcs
* outboundtcpconnection uses per message timeout.
there are still couple of places undetermined.
* FailureDetector.java:249, we need a getGossipTimeout() here?
* MessagingService.java, in expiringMap we probably want getMaxRpcTimeout()
*
StorageService.java:sendReplicationNotification()/truncateResponseHander/FileStreamTask,
we use getGenericRpcTimeout()?
* StorageProxy.java, 3 waitOnFutures calls for repairs, they should bear the
timeout of the enclosing call?
* StorageProxy.java, describeSchema and truncate should use
getGenericRpcTimeout()?
* OutboundTcpConnection.java, in connect(), shall we have a getSocketTimeout()
or use getGenericRpcTimeout()?
> 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-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
