You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ryan McGuire (JIRA)" <ji...@apache.org> on 2013/06/19 01:24:21 UTC

[jira] [Commented] (CASSANDRA-5658) TracingStage frequently times out

    [ https://issues.apache.org/jira/browse/CASSANDRA-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687368#comment-13687368 ] 

Ryan McGuire commented on CASSANDRA-5658:
-----------------------------------------

I see the following in the system_trace keyspace:

{code}
cqlsh:system_traces> select * FROM sessions 
                 ... ;

 session_id                           | coordinator | duration | parameters                                                   | request            | started_at
--------------------------------------+-------------+----------+--------------------------------------------------------------+--------------------+--------------------------
 396cb7b0-d86c-11e2-8be4-35db2404c433 |   127.0.0.1 | 10062609 | {query: INSERT INTO test.test (id, value) VALUES (1, 'one')} | execute_cql3_query | 2013-06-18 19:10:10-0400

cqlsh:system_traces> select * from events WHERE session_id = 396cb7b0-d86c-11e2-8be4-35db2404c433;

 session_id                           | event_id                             | activity                                                    | source    | source_elapsed | thread
--------------------------------------+--------------------------------------+-------------------------------------------------------------+-----------+----------------+------------------
 396cb7b0-d86c-11e2-8be4-35db2404c433 | 396e1740-d86c-11e2-8be4-35db2404c433 | Parsing INSERT INTO test.test (id, value) VALUES (1, 'one') | 127.0.0.1 |           5622 |         Thrift:1
 396cb7b0-d86c-11e2-8be4-35db2404c433 | 396e3e50-d86c-11e2-8be4-35db2404c433 |                                          Peparing statement | 127.0.0.1 |           6636 |         Thrift:1
 396cb7b0-d86c-11e2-8be4-35db2404c433 | 39760680-d86c-11e2-8be4-35db2404c433 |                               Sending message to /127.0.0.2 | 127.0.0.1 |          57681 | WRITE-/127.0.0.2
 396cb7b0-d86c-11e2-8be4-35db2404c433 | 3f6c35a0-d86c-11e2-8be4-35db2404c433 |                                               Write timeout | 127.0.0.1 |       10059608 |         Thrift:1
{code}
                
> TracingStage frequently times out
> ---------------------------------
>
>                 Key: CASSANDRA-5658
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5658
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 2.0
>            Reporter: Ryan McGuire
>         Attachments: system.log, 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