[
https://issues.apache.org/jira/browse/CASSANDRA-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812115#comment-13812115
]
Jonathan Ellis commented on CASSANDRA-4705:
-------------------------------------------
No.
> Speculative execution for reads / eager retries
> -----------------------------------------------
>
> Key: CASSANDRA-4705
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4705
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Vijay
> Assignee: Vijay
> Fix For: 2.0 beta 1
>
> Attachments: 0001-CASSANDRA-4705-v2.patch,
> 0001-CASSANDRA-4705-v3.patch, 0001-CASSANDRA-4705.patch,
> 0001-Refactor-to-introduce-AbstractReadExecutor.patch,
> 0002-Add-Speculative-execution-for-Row-Reads.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 was sent by Atlassian JIRA
(v6.1#6144)
