[
https://issues.apache.org/jira/browse/CASSANDRA-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058113#comment-13058113
]
Melvin Wang commented on CASSANDRA-2819:
----------------------------------------
yep, a simple look up will do. I guess I was confused by Request_Response
messages. When we create request_response we don't record which type of message
it replies to so in MessageDeliveryTask it's difficult to figure it out. Thus I
wanted some way to associate the info to the request_response messages so that
we could better time them out in MessageDeliveryTask. This is certainly
complicated.
Also in OutboundTcpConnection we better honor the per-verb timeout as well by
providing a way to set the timeout value before we try to connect. If we want
to hardcode, then it needs to be the max of (read, range read, write) since it
lies on the path of these operations.
> 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
