cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (JIRA)" <>
Subject [jira] [Resolved] (CASSANDRA-2698) Instrument repair to be able to assess it's efficiency (precision)
Date Wed, 07 Aug 2013 18:00:52 GMT


Yuki Morishita resolved CASSANDRA-2698.

       Resolution: Fixed
    Fix Version/s: 2.0.1

Thanks for the patch.

I committed the patch to be released in 2.0.1, with nit style fix and type change(int to long
in CountingDigest.count).

We can change the log output in the future if needed.
> Instrument repair to be able to assess it's efficiency (precision)
> ------------------------------------------------------------------
>                 Key: CASSANDRA-2698
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Sylvain Lebresne
>            Assignee: Benedict
>            Priority: Minor
>              Labels: lhf
>             Fix For: 2.0.1
>         Attachments: nodetool_repair_and_cfhistogram.tar.gz, patch_2698_v1.txt, patch.diff,
patch-rebased.diff, patch.taketwo.alpha.diff, patch.taketwo.forreview.diff, trunk-2698.txt
> 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.   

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:

View raw message