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

Posted to commits@cassandra.apache.org by "Stu Hood (JIRA)" <ji...@apache.org> on 2011/06/24 03:15:47 UTC

[jira] [Issue Comment Edited] (CASSANDRA-2819) Split rpc timeout for read and write ops

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

Stu Hood edited comment on CASSANDRA-2819 at 6/24/11 1:14 AM:
--------------------------------------------------------------

This issue relates to 959, which additionally proposed splitting out timeouts for multi-row operations, which is slightly more challenging. EDIT: And not worth doing here, imo.

      was (Author: stuhood):
    This issue relates to 959, which additionally proposed splitting out timeouts for multi-row operations, which is slightly more challenging.
  
> 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
>             Fix For: 1.0
>
>
> 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