cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-2819) Split rpc timeout for read and write ops
Date Wed, 16 May 2012 20:45:11 GMT


Jonathan Ellis updated CASSANDRA-2819:

    Attachment: 2819-v8.txt

v8 adds truncate timeout and rebases.

I don't think separate gossip or socket timeouts are crucial.  Happy to leave them using the
generic one.

Updated the repair waits to use write timeout.

Still todo:

- handle expiringmap somehow.  max(timeouts) would be technically correct but with truncate
taking a (much) longer timeout (since it has to wait for compaction to finish), that could
leave a lot of garbage in the map

> Split rpc timeout for read and write ops
> ----------------------------------------
>                 Key: CASSANDRA-2819
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Stu Hood
>            Assignee: Melvin Wang
>             Fix For: 1.1.1
>         Attachments: 2819-v4.txt, 2819-v5-rebased.txt, 2819-v8.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