cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vijay (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-4705) Speculative execution for CL_ONE
Date Thu, 04 Oct 2012 00:37:08 GMT


Vijay updated CASSANDRA-4705:

    Attachment: 0001-CASSANDRA-4705.patch

Hi Jonathan, the custom value is kind of better in the cases where users can say, My SLA is
20 MS and i want co-ordinator to retry the reads after 15 MS, or more aggressively retry after
10 MS.

Attached patch supports the following:

- auto95 (Default)
- auto98
- auto99
- auto999
- autoMean
- NONE (current behavior)

> Speculative execution for CL_ONE
> --------------------------------
>                 Key: CASSANDRA-4705
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>    Affects Versions: 1.2.0
>            Reporter: Vijay
>            Assignee: Vijay
>            Priority: Minor
>         Attachments: 0001-CASSANDRA-4705.patch
> When read_repair is not 1.0, we send the request to one node for some of the requests.
When a node goes down or when a node is too busy the client has to wait for the timeout before
it can retry. 
> It would be nice to watch for latency and execute an additional request to a different
node, if the response is not received within average/99% of the response times recorded in
the past.
> CASSANDRA-2540 might be able to solve the variance when read_repair is set to 1.0
> 1) May be we need to use metrics-core to record various Percentiles
> 2) Modify ReadCallback.get to execute additional request speculatively.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message