cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vijay (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2819) Split rpc timeout for read and write ops
Date Fri, 22 Jun 2012 00:54:42 GMT


Vijay commented on CASSANDRA-2819:

The target can be null when the host is killed before it fires
I think the NPE is because CallbackInfo.sentMessage is null right? 
i think it is better to move store the timeout value in the CallbackInfo...

> Split rpc timeout for read and write ops
> ----------------------------------------
>                 Key: CASSANDRA-2819
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Stu Hood
>            Assignee: Jonathan Ellis
>             Fix For: 1.2
>         Attachments: 2819-v4.txt, 2819-v5-rebased.txt, 2819-v8.txt, 2819-v9.txt, c2819-v6,
c2819-v7, 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:!default.jspa
For more information on JIRA, see:


View raw message