cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan McGuire (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-5658) TracingStage frequently times out
Date Wed, 19 Jun 2013 05:03:19 GMT

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

Ryan McGuire edited comment on CASSANDRA-5658 at 6/19/13 5:01 AM:
------------------------------------------------------------------

trace_bug_cqlsh.py is an alternative test that does not use cassandra-dbapi2, instead it just
forks cqlsh and runs the same queries loaded from a file (trace_bug.cql). I get the same exception
that way.
                
      was (Author: enigmacurry):
    trace_bug_cqlsh.py is an alternative test that does not use cassandra-dbapi2, instead
it just forks cqlsh and runs the same queries loaded from a file (trace_bug.cql). I get the
same exception that way.

The system_traces.events has slightly different wording:
{code}
cqlsh> select * from system_traces.events;

 session_id                           | event_id                             | activity  
                                                  | source    | source_elapsed | thread
--------------------------------------+--------------------------------------+--------------------------------------------------------------+-----------+----------------+------------------
 59128560-d89c-11e2-a26b-35db2404c433 | 59143310-d89c-11e2-a26b-35db2404c433 | Parsing INSERT
INTO test.test (id, value) VALUES (1, 'one'); | 127.0.0.1 |           8329 |         Thrift:1
 59128560-d89c-11e2-a26b-35db2404c433 | 59145a20-d89c-11e2-a26b-35db2404c433 |           
                               Peparing statement | 127.0.0.1 |           9262 |         Thrift:1
 59128560-d89c-11e2-a26b-35db2404c433 | 59148130-d89c-11e2-a26b-35db2404c433 |           
                Determining replicas for mutation | 127.0.0.1 |          10112 |         Thrift:1
 59128560-d89c-11e2-a26b-35db2404c433 | 591f2f90-d89c-11e2-a26b-35db2404c433 |           
                    Sending message to /127.0.0.2 | 127.0.0.1 |          80266 | WRITE-/127.0.0.2
 59128560-d89c-11e2-a26b-35db2404c433 | 5f1537a0-d89c-11e2-a26b-35db2404c433 |           
  Write timeout; received 0 of 1 required replies | 127.0.0.1 |       10081364 |         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: 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

Mime
View raw message