Closed rahuljayz closed 7 years ago
Hi @rahuljayz:
When any unknown error happens in cassandra server code and it does not return any rows to client, it returns that 1300 error code. It is not descriptive about the error.
You must look for this error cause in server logs/system.log or logs/debug.log
It is posible to configure a logger for exceptions generated in cassandra-lucene-index classes just adding a new line to the end of $CASSANDRAHOME/conf/logback.xml and restart cassandra.
<root level="INFO">
<appender-ref ref="SYSTEMLOG" />
<appender-ref ref="STDOUT" />
<appender-ref ref="ASYNCDEBUGLOG" /> <!-- Comment this line to disable debug.log -->
<!--
<appender-ref ref="LogbackMetrics" />
-->
</root>
**<logger name="com.stratio" level="ERROR"/>**
<logger name="org.apache.cassandra" level="DEBUG"/>
<logger name="com.thinkaurelius.thrift" level="ERROR"/>
</configuration>
Does this issue happen in cassandra-lucene-index:3.9.6?
Yes, the problem was somewhere else. You may close this.
hi, what was the problem?
I am getting the same error and struggling for sol badly?
version
This happened to me too! Cassandra version 3.11.1
Everything works fine for one table. In the same keyspace, for another table it does not. Details below:
Cassandra version: 3.9 cassandra-lucene-index-plugin-3.9.0
ReadFailure: Error from server: 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'}