[
https://issues.apache.org/jira/browse/CASSANDRA-959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12862211#action_12862211
]
Jonathan Ellis commented on CASSANDRA-959:
------------------------------------------
Thinking "base timeout + N ms per row" is a better way to go than one-size-fits
all "multirow timeout."
> Allow different timeouts for different classes of operation
> -----------------------------------------------------------
>
> Key: CASSANDRA-959
> URL: https://issues.apache.org/jira/browse/CASSANDRA-959
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 0.7
>
>
> Currently we have one rpc timeout for intra-node operations. But applying
> the same timeout to "read one row", "read multiple rows [by key]," and "range
> query multiple rows" feels like an increasingly uncomfortable fit. (See e.g.
> CASSANDRA-919.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.