[
https://issues.apache.org/jira/browse/CASSANDRA-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759512#action_12759512
]
Hudson commented on CASSANDRA-437:
----------------------------------
Integrated in Cassandra #208 (See
[http://hudson.zones.apache.org/hudson/job/Cassandra/208/])
record gossipped enpoint/token pairs as we see them. also clean up
SystemTable code to avoid unnecessary CF fetches. patch by Gary Dusbabek and
jbellis for
> record token/endpoint (ip) pairs in system table
> ------------------------------------------------
>
> Key: CASSANDRA-437
> URL: https://issues.apache.org/jira/browse/CASSANDRA-437
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jonathan Ellis
> Assignee: Gary Dusbabek
> Fix For: 0.5
>
> Attachments: cassandra-437.diff
>
>
> Each node records its own token after generating one or reading it from the
> config file. For more redundancy we should record others' tokens too.
> This should not be regarded as canonical information -- do not use it to take
> shortcuts instead of using gossip. It is only to provide redundancy in case
> of failure.
> For instance, if your cluster loses power and when it comes back up, the disk
> w/ token information on one of your machines is dead, this will let you get
> that token information easily from another node instead of having to guess by
> scanning sstables. This is not a theoretical scenario; something of this
> nature did happen to FB.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
