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

["Jonathan Ellis (Updated) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-2819:
--------------------------------------

    Attachment: 2819-v5-rebased.txt

rebased to trunk.  (IAsyncCancellableCallback is not included in the patch, so I took my best guess at one.)

Comments:
- Writes still use the old rpc_timeout
- would prefer to rename old rpc_timeout to other_rpc_timout and comment what it's used for (truncate, ?)
- looks like most remaining uses of old rpc_timeout should really be max(different timeouts)
- currently, expiring map checks callbacks for expiration every 1/2 of default timeout. This means short timeouts could go much longer than desired, before being cancelled. I see two options: go back to direct await(timeout) in the callback/response handlers, or update EM to scan much more frequently (which could burn a lot of CPU for a system with many outstanding callbacks)
                
> 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.1
>
>         Attachments: 2819-v4.txt, 2819-v5-rebased.txt, c2819.patch, rpc-jira.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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira