[ https://issues.apache.org/jira/browse/CASSANDRA-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13491369#comment-13491369 ]
Stefan Fleiter commented on CASSANDRA-4482: ------------------------------------------- Won't the in-memory trees still be useful especially for doing repairs under heavy load situation? With Apache Cassandra Anti Entropy finding the inconsistencies adds a big additional load on the servers while with continuous Anti Entropy only the amount of inconsistencies adds load. A cheap continuous Anti Entropy which repairs more than 99% of all inconsistencies automatically and can be active even if the cluster is under heavy load seems beneficial to me. This is especially the case if QUORUM read/writes can not used or for a recovering cluster after an outage of several nodes for more than max_hint_window_in_ms. Getting things 100% correct can for some scenarios wait for a longer time than repairing most inconsistencies. > 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 For more information on JIRA, see: http://www.atlassian.com/software/jira