[
https://issues.apache.org/jira/browse/CASSANDRA-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763471#action_12763471
]
Hudson commented on CASSANDRA-385:
----------------------------------
Integrated in Cassandra #221 (See
[http://hudson.zones.apache.org/hudson/job/Cassandra/221/])
rename getMessagingInstance -> instance; r/m unused methods from
FBUtiltities
patch by jbellis; reviewed by Eric Evans for
get token on bootstrap that gives us half of the keys from the most
heavily-loaded node. (the "splits" approach should also be useful for #342;
adding it to Thrift is trivial)
patch by jbellis; reviewed by Eric Evans for
add getLoadMap jmx method; add load info to nodeprobe ring
patch by jbellis; reviewed by Eric Evans for
use Strings instead of Endpoints in jmx methods. merge cluster info into ring.
patch by jbellis; reviewed by Eric Evans for
move javadoc into mbean. inline methods where wrapping is not necessary to
satisfy Demeter
patch by jbellis; reviewed by Eric Evans for
make LoadInfo a double instead of going from long -> string -> LoadInfo -> int
patch by jbellis; reviewed by Eric Evans for
clean up loadinfo and SLB
patch by jbellis; reviewed by Eric Evans for
> intellibootstrap
> ----------------
>
> Key: CASSANDRA-385
> URL: https://issues.apache.org/jira/browse/CASSANDRA-385
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Fix For: 0.5
>
> Attachments: 0001-CASSANDRA-385-clean-up-loadinfo-and-SLB.txt,
> 0002-make-LoadInfo-a-double-instead-of-going-from-long-s.txt,
> 0003-move-javadoc-into-mbean.-inline-methods-where-wrappin.txt,
> 0004-use-Strings-instead-of-Endpoints-in-jmx-methods.-merge.txt,
> 0005-add-getLoadMap-jmx-method-add-load-info-to-nodeprobe.txt,
> 0006-get-token-on-bootstrap-that-gives-us-half-of-the-keys.txt,
> 0007-switch-to-messagingservice-to-get-bootstrap-token.patch,
> 0008-rename-getMessagingInstance-instance-r-m-unused.patch
>
>
> 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.
