Streaming task hangs forever during repair after unexpected connection reset by 
peer
------------------------------------------------------------------------------------

                 Key: CASSANDRA-3776
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3776
             Project: Cassandra
          Issue Type: Bug
    Affects Versions: 1.0.7
         Environment: Windows Server 2008 R2
Sun Java 7u2 64bit
            Reporter: Viktor Jevdokimov


During streaming (repair) a stream receiving node thrown an exceptions:

ERROR [Streaming:1] 2012-01-24 10:17:03,828 AbstractCassandraDaemon.java (line 
139) Fatal exception in thread Thread[Streaming:1,1,main]
java.lang.RuntimeException: java.net.SocketException: Connection reset by peer: 
socket write error
        at 
org.apache.cassandra.utils.FBUtilities.unchecked(FBUtilities.java:689)
        at 
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:34)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
Caused by: java.net.SocketException: Connection reset by peer: socket write 
error
        at java.net.SocketOutputStream.socketWrite0(Native Method)
        at java.net.SocketOutputStream.socketWrite(Unknown Source)
        at java.net.SocketOutputStream.write(Unknown Source)
        at 
com.ning.compress.lzf.LZFChunk.writeCompressedHeader(LZFChunk.java:77)
        at 
com.ning.compress.lzf.ChunkEncoder.encodeAndWriteChunk(ChunkEncoder.java:132)
        at 
com.ning.compress.lzf.LZFOutputStream.writeCompressedBlock(LZFOutputStream.java:203)
        at com.ning.compress.lzf.LZFOutputStream.write(LZFOutputStream.java:97)
        at 
org.apache.cassandra.streaming.FileStreamTask.write(FileStreamTask.java:181)
        at 
org.apache.cassandra.streaming.FileStreamTask.stream(FileStreamTask.java:145)
        at 
org.apache.cassandra.streaming.FileStreamTask.runMayThrow(FileStreamTask.java:91)
        at 
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
        ... 3 more
ERROR [Streaming:1] 2012-01-24 10:17:03,891 AbstractCassandraDaemon.java (line 
139) Fatal exception in thread Thread[Streaming:1,1,main]
java.lang.RuntimeException: java.net.SocketException: Connection reset by peer: 
socket write error
        at 
org.apache.cassandra.utils.FBUtilities.unchecked(FBUtilities.java:689)
        at 
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:34)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
Caused by: java.net.SocketException: Connection reset by peer: socket write 
error
        at java.net.SocketOutputStream.socketWrite0(Native Method)
        at java.net.SocketOutputStream.socketWrite(Unknown Source)
        at java.net.SocketOutputStream.write(Unknown Source)
        at 
com.ning.compress.lzf.LZFChunk.writeCompressedHeader(LZFChunk.java:77)
        at 
com.ning.compress.lzf.ChunkEncoder.encodeAndWriteChunk(ChunkEncoder.java:132)
        at 
com.ning.compress.lzf.LZFOutputStream.writeCompressedBlock(LZFOutputStream.java:203)
        at com.ning.compress.lzf.LZFOutputStream.write(LZFOutputStream.java:97)
        at 
org.apache.cassandra.streaming.FileStreamTask.write(FileStreamTask.java:181)
        at 
org.apache.cassandra.streaming.FileStreamTask.stream(FileStreamTask.java:145)
        at 
org.apache.cassandra.streaming.FileStreamTask.runMayThrow(FileStreamTask.java:91)
        at 
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
        ... 3 more

After which streaming hanged forever.

A few seconds later the sending node had an exception (may not be related):
ERROR [Thread-17224] 2012-01-24 10:17:07,817 AbstractCassandraDaemon.java (line 
139) Fatal exception in thread Thread[Thread-17224,5,main]
java.lang.ArrayIndexOutOfBoundsException

Other than that, nodes behave normally, communicating each other.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to