[
https://issues.apache.org/jira/browse/CASSANDRA-5263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-5263:
--------------------------------------
Component/s: (was: Config)
Fix Version/s: 2.1.1
Assignee: Yuki Morishita (was: Minh Do)
Summary: Increase merkle tree depth as needed (was: Allow Merkle
tree maximum depth to be configurable)
> Increase merkle tree depth as needed
> ------------------------------------
>
> Key: CASSANDRA-5263
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5263
> Project: Cassandra
> Issue Type: Improvement
> Affects Versions: 1.1.9
> Reporter: Ahmed Bashir
> Assignee: Yuki Morishita
> Fix For: 2.1.1
>
>
> Currently, the maximum depth allowed for Merkle trees is hardcoded as 15.
> This value should be configurable, just like phi_convict_treshold and other
> properties.
> Given a cluster with nodes responsible for a large number of row keys, Merkle
> tree comparisons can result in a large amount of unnecessary row keys being
> streamed.
> Empirical testing indicates that reasonable changes to this depth (18, 20,
> etc) don't affect the Merkle tree generation and differencing timings all
> that much, and they can significantly reduce the amount of data being
> streamed during repair.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
