[
https://issues.apache.org/jira/browse/CASSANDRA-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-128:
-------------------------------------
Description:
- should GC tombstones instantly post-handoff since that data is only local
(no need to worry about RR which is the point of tombstoning)
- waiting for ack-per-key in HHM.sendMessage is going to really slow things
down since you spend most of your time waiting for acks
was:
- now that we have range queries we can split the HH keys across a standard CF
instead of a single row in a super CF
- should GC tombstones instantly post-handoff since that data is only local
(no need to worry about RR which is the point of tombstoning)
- waiting for ack-per-key in HHM.sendMessage is going to really slow things
down since you spend most of your time waiting for acks
Originally included
- now that we have range queries we can split the HH keys across a standard CF
instead of a single row in a super CF
Answer is no, we don't want to make HH dependent on partitioner type.
> Hinted handoff improvements
> ---------------------------
>
> Key: CASSANDRA-128
> URL: https://issues.apache.org/jira/browse/CASSANDRA-128
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Jonathan Ellis
> Priority: Minor
>
> - should GC tombstones instantly post-handoff since that data is only local
> (no need to worry about RR which is the point of tombstoning)
> - waiting for ack-per-key in HHM.sendMessage is going to really slow things
> down since you spend most of your time waiting for acks
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
