cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stu Hood (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-657) AntiEntropyService causes lots of errors to be logged during unit tests
Date Tue, 29 Dec 2009 22:50:29 GMT


Stu Hood commented on CASSANDRA-657:

Ah yea. I've seen this one before: it seems to happen after successful streaming sessions,
but because streaming is a bit of a black box, I've never looked into it too deeply. We might
want to make this depend on CASSANDRA-579, since changes there will likely expose these inconsistencies.

> AntiEntropyService causes lots of errors to be logged during unit tests
> -----------------------------------------------------------------------
>                 Key: CASSANDRA-657
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.9
>            Reporter: Jonathan Ellis
>            Assignee: Stu Hood
> Some examples from a successful test run on trunk:
> Reached an EOL or something bizzare occured. Reading from: /
BufferSizeRemaining: 16
> 	at
> 	at
> 	at
> 	at$
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
> 	at java.util.concurrent.ThreadPoolExecutor$
> 	at
> ERROR [TCP Selector Manager] 2009-12-29 16:27:53,244 (line 363) Encountered
IOException on connection: java.nio.channels.SocketChannel[closed]
> Connection refused
> 	at Method)
> 	at
> 	at
> 	at
> 	at
> It's not obvious to me if these are errors in AES, errors in the streaming code, errors
caused because the test environment insufficiently resembles a live one, or errors because
the test is asking the streaming code to do something that doesn't make sense, but AES is
definitely at least immediately responsible.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message