CODEWITHSUNDEEP
javacassandra
Kevin Branigan
Kevin Branigan

Reputation: 223

Cassandra 1.1.1 fails to drop columnfamily

csuser@lovelyserver01:~$ cqlsh --cql3 lovelyserver01
Connected to Lovely Cluster at lovelyserver01:9160.
[cqlsh 2.2.0 | Cassandra 1.1.1 | CQL spec 3.0.0 | Thrift protocol 19.32.0]
Use HELP for help.
cqlsh> CREATE KEYSPACE bigdata WITH strategy_class = 'SimpleStrategy' AND strategy_options:replication_factor=3;
cqlsh> USE bigdata;
cqlsh:bigdata> CREATE COLUMNFAMILY results (client_id int, hierarchy_id int, units int, measures int, PRIMARY KEY (client_id, hierarchy_id));

insert a few rows, anywhere from 5 to 5000 rows - nothing crazy. Then I realize I need to adjust the column family layout and reinsert all the data so I:

cqlsh:bigdata> DROP COLUMNFAMILY results;

This does nothing, no error, the column family still exists and I can still select data from that column family. I do it a few more times and then it seems to work.

Then when I try and recreate the column family, every time I get "TSocket read 0 bytes" and the cqlsh session becomes useless. If I delete the cassandra data directory on all nodes then I can recreate the keyspace and restart. Naturally this has made development rather slow going.

I have tried this on a cluster of 5 older laptops as well as 10 AWS EC2 instances.

Initial tokens for each node is twice the value of the previous. The seed for each node is set up to be the first node. Commitlog is on the same device. I am using the hostname for the listen_address and rpc_address.

Anyone know what the issue may be?

Upvotes: 4

Views: 1322

Answers (2)

Kevin Branigan
Kevin Branigan

Reputation: 223

A combination of:

  • updating to cassandra 1.1.2 (from 1.1.1)
  • installing NTP on all nodes
  • upgrading the file system to ext4 (from ext3)

has fixed this issue.

Upvotes: 3

Kevin Branigan
Kevin Branigan

Reputation: 223

Seems like editing that file 'log4j-server.properties' did not fix the issue.

I have to delete the data on all machines to recreate a column family. This is highly annoying.

Upvotes: 0

Related Questions