cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Greene (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CASSANDRA-362) SystemTable is not persisted across reboots
Date Fri, 14 Aug 2009 03:46:14 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Greene updated CASSANDRA-362:
-------------------------------------

    Component/s: Core

> SystemTable is not persisted across reboots
> -------------------------------------------
>
>                 Key: CASSANDRA-362
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-362
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.4
>            Reporter: Sammy Yu
>            Assignee: Sammy Yu
>             Fix For: 0.4
>
>         Attachments: 0001-Based-on-jbellis-original-patch-3-and-what-I-had-lo.patch,
0001-CASSANDRA-362-rename-underscores-away.txt, 0002-Based-on-jbellis-original-patch-3-and-what-I-had-lo.patch,
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.


Mime
View raw message