cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Dusbabek (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-1146) "Expected both token and generation columns"
Date Fri, 04 Jun 2010 13:04:57 GMT


Gary Dusbabek commented on CASSANDRA-1146:

Right, but you don't want to replay the commit log if someone has changed the partitioner,
do you?  That would be Bad.  The point of this patch is to detect a partitioner mismatch at
the earliest possible moment.  Flushing the CL after updating the system table means that
we have to wait for one less restart for the the system sstable files to appear so that we
can rely on the mismatch detection code to work.

> "Expected both token and generation columns"
> --------------------------------------------
>                 Key: CASSANDRA-1146
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.6
>            Reporter: Jonathan Ellis
>            Assignee: Gary Dusbabek
>             Fix For: 0.6.3
>         Attachments: 0001-detect-partitioner-changes-and-fail-fast.patch
> From the mailing list:
> {code}
> ERROR 16:14:35,975 Exception encountered during startup.
> java.lang.RuntimeException: Expected both token and generation columns; found ColumnFamily(LocationInfo
>     at org.apache.cassandra.db.SystemTable.initMetadata(
>     at org.apache.cassandra.service.StorageService.initServer(
>     at org.apache.cassandra.thrift.CassandraDaemon.setup(
>     at org.apache.cassandra.thrift.CassandraDaemon.main(
> Exception encountered during startup.
> {code}
> Separately, the same user wrote: "I added a server to my cluster. It had some junk in
the system/LocationInfo files from previous, unsuccessful attempts to add the server to the
cluster. (They were unsuccessful because I hadn't opened the port on that computer.)"
> Perhaps that is why it was able to create the Generation column but not the Token?

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

View raw message