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/08/13 23:05:14 UTC
[jira] Updated: (CASSANDRA-362) SystemTable is not persisted across
reboots
[ https://issues.apache.org/jira/browse/CASSANDRA-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-362:
-------------------------------------
Attachment: 0003-fix-incompletely-configured-system-table-and-query-for.txt
0002-rename-getInitialToken-to-getToken-it-doesn-t-actuall.txt
0001-CASSANDRA-362-rename-underscores-away.txt
> SystemTable is not persisted across reboots
> -------------------------------------------
>
> Key: CASSANDRA-362
> URL: https://issues.apache.org/jira/browse/CASSANDRA-362
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.4
> Reporter: Sammy Yu
> Assignee: Sammy Yu
> Fix For: 0.4
>
> Attachments: 0001-CASSANDRA-362-rename-underscores-away.txt, 0002-rename-getInitialToken-to-getToken-it-doesn-t-actuall.txt, 0003-fix-incompletely-configured-system-table-and-query-for.txt
>
>
> If you set InititalToken to "" and restart cassandra it should generate a initialtoken and store it in the SystemTable so that next time it is not regenerated. However, this is not the case as a new inititaltoken is generated every time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.