cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Thompson (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10771) is failing
Date Wed, 25 Nov 2015 17:26:11 GMT


Philip Thompson commented on CASSANDRA-10771:

>From monitoring logs of failing tests, it appears that after node3 has finished streaming
in the data from node1, it never begins listening for CQL clients, so the test never moves
on to bringing node1 back up.

The test failure looks like:

Traceback (most recent call last):
  File "/Users/philipthompson/cstar/cassandra-dtest/", line 253, in wrapped
  File "/Users/philipthompson/cstar/cassandra-dtest/", line 138, in resumable_bootstrap_test
    node3.watch_log_for("Starting listening for CQL clients", timeout=100)
  File "/Users/philipthompson/cstar/ccm/ccmlib/", line 409, in watch_log_for
    raise TimeoutError(time.strftime("%d %b %Y %H:%M:%S", time.gmtime()) + " [" +
+ "] Missing: " + str([e.pattern for e in tofind]) + ":\n" + reads[:50] + ".....\nSee {} for
TimeoutError: 25 Nov 2015 17:13:23 [node3] Missing: ['Starting listening for CQL clients']:
INFO  [main] 2015-11-25 12:11:04,679 YamlConfigura.....
See system.log for remainder

And I see this in node3's log
java.lang.NullPointerException: Cannot suppress a null exception.
	at java.lang.Throwable.addSuppressed( ~[na:1.8.0_51]
	at ~[main/:na]
	at org.apache.cassandra.streaming.messages.IncomingFileMessage$1.deserialize(
	at org.apache.cassandra.streaming.messages.IncomingFileMessage$1.deserialize(
	at org.apache.cassandra.streaming.messages.StreamMessage.deserialize(
	at org.apache.cassandra.streaming.ConnectionHandler$
	at [na:1.8.0_51]

> is failing
> -------------------------------------------------------------------
>                 Key: CASSANDRA-10771
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Streaming and Messaging
>            Reporter: Philip Thompson
>             Fix For: 3.0.1, 3.1
> When running {{}} locally, the
test is failing on cassandra-3.0. When I bisect the failure, I find that 87f5e2e39c100, the
commit that merged CASSANDRA-10557 into 3.0 is the first failing commit. I can reproduce this
consistently locally, but cassci is only having intermittent failures.

This message was sent by Atlassian JIRA

View raw message