Description
Some reports indicate that repair sometime transfer huge amounts of data. One hypothesis is that the merkle tree precision may deteriorate too much at some data size. To check this hypothesis, it would be reasonably to gather statistic during the merkle tree building of how many rows each merkle tree range account for (and the size that this represent). It is probably an interesting statistic to have anyway.
Attachments
Attachments
Issue Links
- is related to
-
CASSANDRA-5398 Remove localTimestamp from merkle-tree calculation (for tombstones)
- Resolved
- relates to
-
CASSANDRA-4905 Repair should exclude gcable tombstones from merkle-tree computation
- Resolved
-
CASSANDRA-4917 Optimize tombstone creation for ExpiringColumns
- Resolved