You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2009/09/10 16:45:00 UTC
[jira] Created: (CASSANDRA-438) autoboostrap
autoboostrap
------------
Key: CASSANDRA-438
URL: https://issues.apache.org/jira/browse/CASSANDRA-438
Project: Cassandra
Issue Type: Improvement
Reporter: Jonathan Ellis
Fix For: 0.5
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.
[jira] Updated: (CASSANDRA-438) autoboostrap
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-438:
-------------------------------------
Attachment: 0003-r-m-nodeprobe-bootstrap.patch
rebase 03
> 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, 0002-add-autobootstrap.txt, 0003-r-m-nodeprobe-bootstrap.patch
>
>
> 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.
[jira] Updated: (CASSANDRA-438) autoboostrap
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-438:
-------------------------------------
Attachment: 0003-r-m-nodeprobe-bootstrap.txt
0002-add-autobootstrap.txt
0001-CASSANDRA-438-rename-LOCATION_CF-STATUS_CF.-cleanu.txt
> 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, 0002-add-autobootstrap.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.
[jira] Updated: (CASSANDRA-438) autoboostrap
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-438:
-------------------------------------
Attachment: 0003-r-m-nodeprobe-bootstrap.txt
0002-add-autobootstrap.txt
0001-CASSANDRA-438-rename-LOCATION_CF-STATUS_CF.-cleanu.txt
> 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, 0002-add-autobootstrap.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.
[jira] Updated: (CASSANDRA-438) autoboostrap
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-438:
-------------------------------------
Attachment: (was: 0001-CASSANDRA-438-rename-LOCATION_CF-STATUS_CF.-cleanu.txt)
> 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, 0002-add-autobootstrap.txt, 0003-r-m-nodeprobe-bootstrap.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.
[jira] Updated: (CASSANDRA-438) autoboostrap
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-438:
-------------------------------------
Attachment: 0003-r-m-nodeprobe-bootstrap.txt
0002-add-autobootstrap.txt
0001-CASSANDRA-438-rename-LOCATION_CF-STATUS_CF.-cleanu.txt
> autoboostrap
> ------------
>
> Key: CASSANDRA-438
> URL: https://issues.apache.org/jira/browse/CASSANDRA-438
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jonathan Ellis
> Fix For: 0.5
>
> Attachments: 0001-CASSANDRA-438-rename-LOCATION_CF-STATUS_CF.-cleanu.txt, 0002-add-autobootstrap.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.
[jira] Commented: (CASSANDRA-438) autoboostrap
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763473#action_12763473 ]
Hudson commented on CASSANDRA-438:
----------------------------------
Integrated in Cassandra #221 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/221/])
r/m nodeprobe bootstrap
patch by jbellis; reviewed by Eric Evans for
add autobootstrap
patch by jbellis; reviewed by Eric Evans for
rename LOCATION_CF -> STATUS_CF. cleanup.
patch by jbellis; reviewed by Eric Evans for
> 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, 0002-add-autobootstrap.txt, 0003-r-m-nodeprobe-bootstrap.txt, 0004-fix-npe.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.
[jira] Commented: (CASSANDRA-438) autoboostrap
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763211#action_12763211 ]
Eric Evans commented on CASSANDRA-438:
--------------------------------------
Looks good. +1
> 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, 0002-add-autobootstrap.txt, 0003-r-m-nodeprobe-bootstrap.txt, 0004-fix-npe.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.
[jira] Updated: (CASSANDRA-438) autoboostrap
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-438:
-------------------------------------
Attachment: 0003-r-m-nodeprobe-bootstrap.txt
0002-add-autobootstrap.txt
0001-CASSANDRA-438-rename-LOCATION_CF-STATUS_CF.-cleanu.txt
> 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.
[jira] Commented: (CASSANDRA-438) autoboostrap
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763123#action_12763123 ]
Eric Evans commented on CASSANDRA-438:
--------------------------------------
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.
[jira] Updated: (CASSANDRA-438) autoboostrap
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-438:
-------------------------------------
Attachment: (was: 0003-r-m-nodeprobe-bootstrap.txt)
> 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, 0002-add-autobootstrap.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.
[jira] Commented: (CASSANDRA-438) autoboostrap
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763114#action_12763114 ]
Jonathan Ellis commented on CASSANDRA-438:
------------------------------------------
rebased again
> 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.
[jira] Updated: (CASSANDRA-438) autoboostrap
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-438:
-------------------------------------
Attachment: 0003-r-m-nodeprobe-bootstrap.txt
0002-add-autobootstrap.txt
0001-CASSANDRA-438-rename-LOCATION_CF-STATUS_CF.-cleanu.txt
> 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, 0002-add-autobootstrap.txt, 0003-r-m-nodeprobe-bootstrap.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.
[jira] Updated: (CASSANDRA-438) autoboostrap
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-438:
-------------------------------------
Attachment: (was: 0002-add-autobootstrap.txt)
> 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, 0002-add-autobootstrap.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.
[jira] Updated: (CASSANDRA-438) autoboostrap
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-438:
-------------------------------------
Attachment: (was: 0001-CASSANDRA-438-rename-LOCATION_CF-STATUS_CF.-cleanu.txt)
> 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, 0002-add-autobootstrap.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.
[jira] Updated: (CASSANDRA-438) autoboostrap
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-438:
-------------------------------------
Attachment: (was: 0003-r-m-nodeprobe-bootstrap.patch)
> 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, 0002-add-autobootstrap.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.
[jira] Issue Comment Edited: (CASSANDRA-438) autoboostrap
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (CASSANDRA-438) autoboostrap
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763141#action_12763141 ]
Jonathan Ellis commented on CASSANDRA-438:
------------------------------------------
oops, rebased better (and compiled :)
> 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, 0002-add-autobootstrap.txt, 0003-r-m-nodeprobe-bootstrap.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.
[jira] Updated: (CASSANDRA-438) autoboostrap
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-438:
-------------------------------------
Attachment: 0004-fix-npe.txt
fix npe by moving bootstrap init into start() after udpaddr is initialized
> 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, 0002-add-autobootstrap.txt, 0003-r-m-nodeprobe-bootstrap.txt, 0004-fix-npe.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.
[jira] Updated: (CASSANDRA-438) autoboostrap
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-438:
-------------------------------------
Attachment: (was: 0003-r-m-nodeprobe-bootstrap.txt)
> 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, 0002-add-autobootstrap.txt, 0003-r-m-nodeprobe-bootstrap.patch
>
>
> 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.
[jira] Updated: (CASSANDRA-438) autoboostrap
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-438:
-------------------------------------
Attachment: (was: 0002-add-autobootstrap.txt)
> 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, 0002-add-autobootstrap.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.
[jira] Updated: (CASSANDRA-438) autoboostrap
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-438:
-------------------------------------
Attachment: (was: 0001-CASSANDRA-438-rename-LOCATION_CF-STATUS_CF.-cleanu.txt)
> 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, 0002-add-autobootstrap.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.