Cassandra 1.1.1未能刪除列家族

[英]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:

插入幾行,從5到5000行 - 沒什么了不起的。然后我意識到我需要調整列族布局並重新插入所有數據,所以我:

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.

然后,當我嘗試重新創建列族時,每次我得到“TSocket讀取0字節”並且cqlsh會話變得無用。如果我刪除所有節點上的cassandra數據目錄,那么我可以重新創建密鑰空間並重新啟動。當然,這使得發展進展緩慢。

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

我在5台舊筆記本電腦的集群以及10個AWS EC2實例上嘗試過此操作。

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.

每個節點的初始令牌是前一個節點的兩倍。每個節點的種子被設置為第一個節點。 Commitlog在同一台設備上。我使用的是listen_address和rpc_address的主機名。

Anyone know what the issue may be?

誰知道問題可能是什么?

2 个解决方案

#1


3  

A combination of:

結合:

  • updating to cassandra 1.1.2 (from 1.1.1)
  • 更新到cassandra 1.1.2(從1.1.1開始)

  • installing NTP on all nodes
  • 在所有節點上安裝NTP

  • upgrading the file system to ext4 (from ext3)
  • 將文件系統升級到ext4(來自ext3)

has fixed this issue.

已修復此問題。

#2


0  

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

似乎編輯該文件'log4j-server.properties'沒有解決問題。

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

我必須刪除所有計算機上的數據才能重新創建列族。這非常煩人。


注意!

本站翻译的文章,版权归属于本站,未经许可禁止转摘,转摘请注明本文地址:https://www.itdaan.com/blog/2012/06/13/720a2fd0217abd67b9cd5f673880be85.html



 
粤ICP备14056181号  © 2014-2020 ITdaan.com