Ahmed Bashir created CASSANDRA-5263:
---------------------------------------
Summary: Allow Merkle tree maximum depth to be configurable
Key: CASSANDRA-5263
URL: https://issues.apache.org/jira/browse/CASSANDRA-5263
Project: Cassandra
Issue Type: Improvement
Components: Config
Affects Versions: 1.1.9
Reporter: Ahmed Bashir
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 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
