cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-2917) expose calculate midrange for token in jmx
Date Wed, 20 Jul 2011 00:27:58 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068087#comment-13068087
] 

Jonathan Ellis commented on CASSANDRA-2917:
-------------------------------------------

Right, that's why I said "Easy: expose gBT."

But again, more useful to expose the sampling data so you can do things like "divide it into
thirds so I can add two nodes."

> expose calculate midrange for token in jmx
> ------------------------------------------
>
>                 Key: CASSANDRA-2917
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2917
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jackson Chung
>            Priority: Minor
>              Labels: lhf
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message