cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (CASSANDRA-438) autoboostrap
Date Wed, 07 Oct 2009 17:08:31 GMT

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

Eric Evans edited comment on CASSANDRA-438 at 10/7/09 10:08 AM:
----------------------------------------------------------------

getCurrentGenerationNumber() was removed from StorageService, but it's still in the MBean
(causing a compilation failure), and is still being called from NodeProbe.printInfo().

      was (Author: urandom):
    getCurrentGenerationNumber() was removed from StorageService, but it's still in the MBean
(causing a compilation failure), and is still be called from NodeProbe.printInfo().
  
> autoboostrap
> ------------
>
>                 Key: CASSANDRA-438
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-438
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>             Fix For: 0.5
>
>         Attachments: 0001-CASSANDRA-438-rename-LOCATION_CF-STATUS_CF.-cleanu.txt, 0001-CASSANDRA-438-rename-LOCATION_CF-STATUS_CF.-cleanu.txt,
0002-add-autobootstrap.txt, 0002-add-autobootstrap.txt, 0003-r-m-nodeprobe-bootstrap.txt,
0003-r-m-nodeprobe-bootstrap.txt
>
>
> We shouldn't have to specify -b manually.
> Instead, a node should *always* initiate bootstrap when it starts up, *unless* it is
a seed node or it has added a flag to its system table that it already completed bootstrap.
 (Seed nodes should add this flag on first startup, so they don't bootstrap mistakenly if
their seed status is removed later.)

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


Mime
View raw message