Forgot to mention that the keyspace 'twitter' was created, then droppend
and re-created a couple of days ago.
How about if I create a new keyspace with the same definition and then
copy the existing tables into the proper place and call nodetool
refresh on each node. Would that work or are there references in the
tables to the keyspace name?
On Wed, Aug 08, 2012 at 03:03:52PM +0200, Arend-Jan Wijtzes wrote:
> Hi,
>
> Today we rebooted a node in our cluster for maintenance and after that
> one of the keyspaces went missing. This is what we did leading up to
> this:
>
> nodetool drain -h localhost
> reboot
>
> restart cassandra
> There was an error during startup:
> ERROR [MutationStage:109] 2012-08-08 14:05:56,443 RowMutationVerbHandler.java
> (line 61) Error in row mutation
> org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find cfId=1014
>
> (then we found keyspace twitter is missing)
>
> The sstables are still there so I tried to re-create the keyspace:
> cassandra-cli -h localhost
> [default@unknown] create keyspace twitter with placement_strategy =
> 'org.apache.cassandra.locator.SimpleStrategy' and strategy_options =
> {replication_factor:3} ;
> b890b65a-40a6-3fc5-838d-34d58368cb64
> Waiting for schema agreement...
> ... schemas agree across the cluster
> NotFoundException()
>
> default@unknown] use twitter;
> Keyspace 'twitter' not found.
>
> So we can't create the keyspace. The cassandra version is 1.1.0.
> What is the proper way to deal with this?
>
> Thanks for your help.
>
> Arend-Jan
> --
> Arend-Jan Wijtzes -- Wiseguys -- www.wise-guys.nl
--
Arend-Jan Wijtzes -- Wiseguys -- www.wise-guys.nl
