[
https://issues.apache.org/jira/browse/CASSANDRA-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13434406#comment-13434406
]
Jonathan Ellis commented on CASSANDRA-4482:
-------------------------------------------
bq. we still recommend that users run either a full repair or a "tombstone-only
repair" at least once every GCGraceSeconds
What is a tombstone-only repair?
If we still need repair every gcgs, I'm not sure how much win there is here,
given that with "durable HH" (CASSANDRA-2034) you only need AES repair when
nodes die (or lose disks) permanently.
Could be interesting to replace TreeRange with your optimized ByteBuffer (or
BigLongArray -- CASSANDRA-3432) though, with or without full "incremental mode"
later. I'd be glad to review a patch along those lines as a first step.
> In-memory merkle trees for repair
> ---------------------------------
>
> Key: CASSANDRA-4482
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4482
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Marcus Eriksson
>
> this sounds cool, we should reimplement it in the open source cassandra;
> http://www.acunu.com/2/post/2012/07/incremental-repair.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
