Cassandra读取错误

tl; dr我解决了升级到Cassandra 3.2的问题。 This bug显然是造成这个问题。Cassandra读取错误

我正在运行Cassandra的双节点集群，其版本号为[cqlsh 5.0.1 | Cassandra 3.0.1 | CQL spec 3.3.1 | Native protocol v4]。

有，我不能读一个表，我有以下错误：

cqlsh:kepler> select type from md_data limit 1; 
Traceback (most recent call last): 
    File "/local/chernals/dsc-cassandra-3.0.1/bin/cqlsh.py", line 1258, in perform_simple_statement 
    result = future.result() 
    File "/local/chernals/dsc-cassandra-3.0.1/bin/../lib/cassandra-driver-internal-only-3.0.0-6af642d.zip/cassandra-driver-3.0.0-6af642d/cassandra/cluster.py", line 3122, in result 
    raise self._final_exception 
ReadFailure: code=1300 [Replica(s) failed to execute read] message="Operation failed - received 0 responses and 1 failures" info={'failures': 1, 'received_responses': 0, 'required_responses': 1, 'consistency': 'ONE'}

我可以读其他表没有任何问题。

该表的模式是：

CREATE TABLE kepler.md_data (
    name text, 
    tag text, 
    id timeuuid, 
    parameter frozen<parameter>, 
    blob_value blob, 
    real_value float, 
    telegram map<text, text> static, 
    text_value text, 
    type text, 
    PRIMARY KEY ((name, tag, id), parameter) 
) WITH CLUSTERING ORDER BY (parameter ASC) 
    AND bloom_filter_fp_chance = 0.01 
    AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'} 
    AND comment = '' 
    AND compaction = {'class': 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy', 'max_threshold': '32', 'min_threshold': '4'} 
    AND compression = {'chunk_length_in_kb': '64', 'class': 'org.apache.cassandra.io.compress.LZ4Compressor'} 
    AND crc_check_chance = 1.0 
    AND dclocal_read_repair_chance = 0.1 
    AND default_time_to_live = 0 
    AND gc_grace_seconds = 864000 
    AND max_index_interval = 2048 
    AND memtable_flush_period_in_ms = 0 
    AND min_index_interval = 128 
    AND read_repair_chance = 0.0 
    AND speculative_retry = '99PERCENTILE'; 
CREATE INDEX parameter_idx ON kepler.md_data (parameter);

会不会有一些问题，这样的模式，我运行不同版本的卡桑德拉/ cqlsh的？

请注意，当表为空时，我可以“读”它（它是空的，但选择语句成功）。

编辑：

，因为我有一个很难复制它所有的时间超奇怪的问题。我转移到只有1节点的测试设置。它似乎与表中存在的行数相关联。

cqlsh:kepler> select type from md_data; 
Traceback (most recent call last): 
    File "/local/chernals/dsc-cassandra-3.0.1/bin/cqlsh.py", line 1258, in perform_simple_statement 
    result = future.result() 
    File "/local/chernals/dsc-cassandra-3.0.1/bin/../lib/cassandra-driver-internal-only-3.0.0-6af642d.zip/cassandra-driver-3.0.0-6af642d/cassandra/cluster.py", line 3122, in result 
    raise self._final_exception 
ReadFailure: code=1300 [Replica(s) failed to execute read] message="Operation failed - received 0 responses and 1 failures" info={'failures': 1, 'received_responses': 0, 'required_responses': 1, 'consistency': 'ONE'} 

cqlsh:kepler> TRUNCATE TABLE md_data; 
cqlsh:kepler> select type from md_data; 

name | tag | id | parameter | blob_value | real_value | telegram | text_value | type 
------+-----+----+-----------+------------+------------+----------+------------+------ 

(0 rows) 
cqlsh:kepler>

编辑：从卡桑德拉错误消息-f

WARN 11:07:00 Uncaught exception on thread Thread[SharedPool-Worker-3,5,main]: {} 
java.lang.AssertionError: null 
    at org.apache.cassandra.db.columniterator.AbstractSSTableIterator$IndexState.updateBlock(AbstractSSTableIterator.java:463) ~[apache-cassandra-3.0.1.jar:3.0.1] 
    at org.apache.cassandra.db.columniterator.SSTableIterator$ForwardIndexedReader.computeNext(SSTableIterator.java:268) ~[apache-cassandra-3.0.1.jar:3.0.1] 
    at org.apache.cassandra.db.columniterator.SSTableIterator$ForwardReader.hasNextInternal(SSTableIterator.java:158) ~[apache-cassandra-3.0.1.jar:3.0.1] 
    at org.apache.cassandra.db.columniterator.AbstractSSTableIterator$Reader.hasNext(AbstractSSTableIterator.java:352) ~[apache-cassandra-3.0.1.jar:3.0.1] 
    at org.apache.cassandra.db.columniterator.AbstractSSTableIterator.hasNext(AbstractSSTableIterator.java:219) ~[apache-cassandra-3.0.1.jar:3.0.1] 
    at org.apache.cassandra.db.columniterator.SSTableIterator.hasNext(SSTableIterator.java:32) ~[apache-cassandra-3.0.1.jar:3.0.1] 
    at org.apache.cassandra.db.transform.BaseRows.hasNext(BaseRows.java:108) ~[apache-cassandra-3.0.1.jar:3.0.1] 
    at org.apache.cassandra.db.rows.UnfilteredRowIteratorSerializer.serialize(UnfilteredRowIteratorSerializer.java:131) ~[apache-cassandra-3.0.1.jar:3.0.1] 
    at org.apache.cassandra.db.rows.UnfilteredRowIteratorSerializer.serialize(UnfilteredRowIteratorSerializer.java:87) ~[apache-cassandra-3.0.1.jar:3.0.1] 
    at org.apache.cassandra.db.rows.UnfilteredRowIteratorSerializer.serialize(UnfilteredRowIteratorSerializer.java:77) ~[apache-cassandra-3.0.1.jar:3.0.1] 
    at org.apache.cassandra.db.partitions.UnfilteredPartitionIterators$Serializer.serialize(UnfilteredPartitionIterators.java:298) ~[apache-cassandra-3.0.1.jar:3.0.1] 
    at org.apache.cassandra.db.ReadResponse$LocalDataResponse.build(ReadResponse.java:136) ~[apache-cassandra-3.0.1.jar:3.0.1] 
    at org.apache.cassandra.db.ReadResponse$LocalDataResponse.<init>(ReadResponse.java:128) ~[apache-cassandra-3.0.1.jar:3.0.1] 
    at org.apache.cassandra.db.ReadResponse$LocalDataResponse.<init>(ReadResponse.java:123) ~[apache-cassandra-3.0.1.jar:3.0.1] 
    at org.apache.cassandra.db.ReadResponse.createDataResponse(ReadResponse.java:65) ~[apache-cassandra-3.0.1.jar:3.0.1] 
    at org.apache.cassandra.db.ReadCommand.createResponse(ReadCommand.java:289) ~[apache-cassandra-3.0.1.jar:3.0.1] 
    at org.apache.cassandra.service.StorageProxy$LocalReadRunnable.runMayThrow(StorageProxy.java:1721) ~[apache-cassandra-3.0.1.jar:3.0.1] 
    at org.apache.cassandra.service.StorageProxy$DroppableRunnable.run(StorageProxy.java:2375) ~[apache-cassandra-3.0.1.jar:3.0.1] 
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[na:1.8.0_66] 
    at org.apache.cassandra.concurrent.AbstractTracingAwareExecutorService$FutureTask.run(AbstractTracingAwareExecutorService.java:164) ~[apache-cassandra-3.0.1.jar:3.0.1] 
    at org.apache.cassandra.concurrent.AbstractTracingAwareExecutorService$TraceSessionFutureTask.run(AbstractTracingAwareExecutorService.java:136) [apache-cassandra-3.0.1.jar:3.0.1] 
    at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105) [apache-cassandra-3.0.1.jar:3.0.1] 
    at java.lang.Thread.run(Thread.java:745) [na:1.8.0_66]

来源

2016-01-15 Cedric H.

1.您是否在Cassandra的日志文件（/var/log/cassandra/system.log）中寻找在非空表上执行SELECT查询时可能出现的错误？ 2.您是否使用Cassandra服务器或其他版本附带的cqlsh版本？ – doanduyhai

是的，执行失败查询时，'tail -f logs/system.log'不显示任何内容。我正在使用Cassandra 3附带的'cqlsh'版本。同样的问题也出现在最新的python驱动程序中。在使用测试数据填充我的数据时，它确实看起来有一些“阈值”：它会在某个点上运行，然后失败。难道有些斑点令Cassandra感到困惑吗？当该表“失败”时，其他人仍然可以。 –

我想这是这个家伙：https://issues.apache.org/jira/browse/CASSANDRA-10903 –

我解决了升级到3.2卡桑德拉的问题。 This bug显然是造成这个问题。

来源

2016-01-15 12:57:31

您是否真的尝试向表中插入一些数据？我在尝试在3.0和3.2中重现此错误时遇到了另一个错误，请参阅[CASSANDRA-11021]（https://issues.apache.org/jira/browse/CASSANDRA-11021） –

我确实也有这个问题。 .. :( –

Cassandra读取错误

回答

相关问题