[
https://issues.apache.org/jira/browse/CASSANDRA-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13075977#comment-13075977
]
Patricio Echague commented on CASSANDRA-2034:
---------------------------------------------
v2 patch replaces v1.
Changes in v2:
- It fixes the add-up timeouts by adding a CreationAwareFuture
- Implements the matrix previously discussed
| Hinted Handoff | Consist. Level |
| on | >=1 | --> wait for hints. We DO NOT notify the
handler with handler.response() for hints;
| on | ANY | --> wait for hints. Responses count towards
consistency.
| off | >=1 | --> DO NOT fire hints. And DO NOT wait for
them to complete.
| off | ANY | --> DO NOT fire hints. And DO NOT wait for
them to complete.
> Make Read Repair unnecessary when Hinted Handoff is enabled
> -----------------------------------------------------------
>
> Key: CASSANDRA-2034
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2034
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Patricio Echague
> Fix For: 1.0
>
> Attachments: CASSANDRA-2034-trunk-v2.patch, CASSANDRA-2034-trunk.patch
>
> Original Estimate: 8h
> Remaining Estimate: 8h
>
> Currently, HH is purely an optimization -- if a machine goes down, enabling
> HH means RR/AES will have less work to do, but you can't disable RR entirely
> in most situations since HH doesn't kick in until the FailureDetector does.
> Let's add a scheduled task to the mutate path, such that we return to the
> client normally after ConsistencyLevel is achieved, but after RpcTimeout we
> check the responseHandler write acks and write local hints for any missing
> targets.
> This would making disabling RR when HH is enabled a much more reasonable
> option, which has a huge impact on read throughput.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
