cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David B (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4444) Failure to delete column families
Date Wed, 18 Jul 2012 22:25:35 GMT


David B commented on CASSANDRA-4444:

In the most recent test, it did delete the metadata.  I wasn't aware of the modifications
introduced in CASSANDRA-4221--thanks for the pointer. 

Running the same test multiple times yesterday, however, got the server into a state where
it would not delete the CF from keyspace metadata.  I had to delete and rebuild the system
keyspace for the system to return to "normal operation".  Symptoms were very similar to what
is reported in  Any chance they could
be related.

In the meantime I'll try to reproduce the erroneous state. Thanks for the quick response!

> Failure to delete column families
> ---------------------------------
>                 Key: CASSANDRA-4444
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1.2
>         Environment: 2 node cluster running on Ubuntu Precise
>            Reporter: David B
>            Assignee: Pavel Yaskevich
> I have a two node cluster, and one keyspace defined as follows:
> create keyspace SampleKeyspace with placement_strategy = 'org.apache.cassandra.locator.SimpleStrategy'
and strategy_options = {replication_factor:2};
> I then create a column family as follows:
> create column family SampleFamily with caching = 'keys_only' and key_validation_class
= 'LongType' and compression_options = { sstable_compression: SnappyCompressor, chunk_length_kb:
64 }
> I stream SSTables through SStableLoader.
> After the load is complete, compaction begins.  During this time, I request a drop of
the family through cassandra-cli using "drop column family SampleFamily".  
> Cassandra-cli responds that schemas are in agreement.  Looking on the file system, however,
the full set of data files are still found under data/SampleFamily (in addition to the snapshot
created on drop family).  There are no errors in either system or output logs. 

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