You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Michael Greene (JIRA)" <ji...@apache.org> on 2009/08/20 06:10:14 UTC

[jira] Updated: (CASSANDRA-385) intellibootstrap

     [ https://issues.apache.org/jira/browse/CASSANDRA-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Greene updated CASSANDRA-385:
-------------------------------------

    Component/s: Core

> intellibootstrap
> ----------------
>
>                 Key: CASSANDRA-385
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-385
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Jonathan Ellis
>
> ideally bootstrap mode should determine its new position on the ring by examining the Load of the existing nodes in the cluster.  (currently Load is just disk space used but making this pluggable is another ticket.)  having found the highest-load-node-that-is-not-participating-in-bootstrap, it should ask that node for a Token which would move half the keys over to the new node.
> This is easily computed since we have a periodic sampling of keys in memory of all the keys on disk, and even SSTable.getIndexedKeys that merges all such keys.  So pick the midpoint, and turn it into a token (these are decorated keys so that is always possible).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.