[
https://issues.apache.org/jira/browse/CASSANDRA-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687621#comment-13687621
]
Jonathan Ellis commented on CASSANDRA-5658:
-------------------------------------------
I thought we had a warning for when we have to drop a mutation on the floor b/c
the table doesn't exist yet. If you don't see anything like that in the log we
should probably add it back. (And if it is in the log, we should add a Tracing
entry as well.)
> TracingStage frequently times out
> ---------------------------------
>
> Key: CASSANDRA-5658
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5658
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.2.4, 1.2.6, 2.0
> Reporter: Ryan McGuire
> Attachments: 5658-logs.tar.gz, trace_bug.cql, trace_bug_cqlsh.py,
> trace_bug.py
>
>
> I am seeing frequent timeout errors when doing programmatic traces via
> trace_next_query()
> {code}
> ERROR [TracingStage:1] 2013-06-18 19:10:20,669 CassandraDaemon.java (line
> 196) Exception in thread Thread[TracingStage:1,5,main]
> java.lang.RuntimeException:
> org.apache.cassandra.exceptions.WriteTimeoutException: Operation timed out -
> received only 0 responses.
> at com.google.common.base.Throwables.propagate(Throwables.java:160)
> at
> org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:32)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:722)
> Caused by: org.apache.cassandra.exceptions.WriteTimeoutException: Operation
> timed out - received only 0 responses.
> at
> org.apache.cassandra.service.AbstractWriteResponseHandler.get(AbstractWriteResponseHandler.java:81)
> at
> org.apache.cassandra.service.StorageProxy.mutate(StorageProxy.java:454)
> at
> org.apache.cassandra.tracing.TraceState$1.runMayThrow(TraceState.java:100)
> at
> org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
> ... 3 more
> {code}
> Attached is the sample code which produced this error and the logs. The error
> occurs directly after the INSERT statement.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
