cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Schrauwen (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3060) Boostrapping node stuck after receiving file with version mismatch
Date Mon, 17 Oct 2011 06:18:13 GMT


Benjamin Schrauwen commented on CASSANDRA-3060:

I would expect Cassandra to manage its own internal file updating.
Pushing this on to the user (without any documentation) is unexpected
and undesired...

Op 15-okt.-2011 om 06:04 heeft "Jonathan Ellis (Resolved) (JIRA)"

> Boostrapping node stuck after receiving file with version mismatch
> ------------------------------------------------------------------
>                 Key: CASSANDRA-3060
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8.3
>            Reporter: Benjamin Schrauwen
>            Priority: Minor
> When adding a node to the cluster, the boostrapping process get's stuck when it receives
a file which is apparently from an older version. This is the Exception
> java.lang.RuntimeException: Cannot recover SSTable /var/lib/cassandra/data/Mollom/recent_sessions-tmp-f-1
due to version mismatch. (current version is g).
>         at
>         at org.apache.cassandra.db.compaction.CompactionManager.submitSSTableBuild(
>         at org.apache.cassandra.streaming.StreamInSession.finished(
>         at org.apache.cassandra.streaming.IncomingStreamReader.readFile(
>         at
>         at
>         at

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message