You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2011/06/29 02:28:28 UTC

[jira] [Commented] (CASSANDRA-959) Allow different timeouts for different classes of operation

    [ https://issues.apache.org/jira/browse/CASSANDRA-959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13056909#comment-13056909 ] 

Jonathan Ellis commented on CASSANDRA-959:
------------------------------------------

Resurrected in CASSANDRA-2819.

> 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
>            Priority: Minor
>             Fix For: 0.8 beta 1
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira