[
https://issues.apache.org/jira/browse/CASSANDRA-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058101#comment-13058101
]
Melvin Wang commented on CASSANDRA-2819:
----------------------------------------
a better way to go would be that we make the timeout part of Message obj so
that when adding callback in MessagingService, we can pass in proper timeout to
ExpiringMap and also in MessageDeliveryTask we can drop the message based on
its own timeout. Not sure how complicated this is would be though.
OutboundTcpConnection uses getRpcTimeout during connection which is a surprise
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.0
>
> Attachments: rpc-rw-timeouts.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
