cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2917) expose calculate midrange for token in jmx
Date Tue, 07 Feb 2012 23:46:59 GMT


Jonathan Ellis commented on CASSANDRA-2917:

Thanks for the patch, Sam!

I think that like the bootstrap token calculator we want to skip the System keyspace here.
 I've added a followup patch that does that over on,
with some refactoring to use the more-efficient CFS.keySamples method.  What do you think?

(P.S. As a style note, I also dropped the Transform business -- while I'm a fan of functional
programmming, it's not always a great fit in Java and for simple cases like this is substantially
more verbose than the imperative version.)

> expose calculate midrange for token in jmx
> ------------------------------------------
>                 Key: CASSANDRA-2917
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jackson Chung
>            Priority: Minor
>              Labels: lhf
>         Attachments: trunk-2917.txt
> currently there is no easy way to get midrange, especially for OPP. For simplicity, you
could call OrderPreservingPartitioner.midpoint(Token, Token), that gives you a rough estimate
(and you'd still need to remove non-utf8 characters.)
> A more accurate but difficult way is to sample the keys in that range and pick the midpoint
of those. We should expose that via jmx, because without this, supporting OPP w/o this is
quite challenging.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message