[
https://issues.apache.org/jira/browse/CASSANDRA-10770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15083772#comment-15083772
]
Robert Stupp commented on CASSANDRA-10770:
------------------------------------------
[~carlo_4002] it seems you're just overloading the cluster and your clients
disconnect and C* is then unable to send the response back (thus the "Socket
closed" in a "socketWrite" method). Hinted handoffs can occur too, if you put
too much load on your cluster. I don't think this is a bug.
> Warning TIOStreamTransport.java:112 - Error closing output stream.
> ------------------------------------------------------------------
>
> Key: CASSANDRA-10770
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10770
> Project: Cassandra
> Issue Type: Bug
> Environment: Cassandra 2.1.11, ubuntu 12.04
> Reporter: jean carlo rivera ura
> Labels: stress-mode, thrift
> Attachments: warning-thrift.txt
>
>
> Hi, In our cluster cassandra of 6 nodes we are having many times the next
> warning
> WARN [Thrift:2477] 2015-11-25 10:06:33,795 TIOStreamTransport.java:112 -
> Error closing output stream.
> java.net.SocketException: Socket closed
> at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:116)
> ~[na:1.8.0_60]
> at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
> ~[na:1.8.0_60]
> at
> java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
> ~[na:1.8.0_60]
> at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
> ~[na:1.8.0_60]
> at java.io.FilterOutputStream.close(FilterOutputStream.java:158)
> ~[na:1.8.0_60]
> at
> org.apache.thrift.transport.TIOStreamTransport.close(TIOStreamTransport.java:110)
> ~[libthrift-0.9.2.jar:0.9.2]
> at
> org.apache.cassandra.thrift.TCustomSocket.close(TCustomSocket.java:197)
> [apache-cassandra-2.1.11.jar:2.1.11]
> at
> org.apache.thrift.transport.TFramedTransport.close(TFramedTransport.java:89)
> [libthrift-0.9.2.jar:0.9.2]
> at
> org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run(CustomTThreadPoolServer.java:231)
> [apache-cassandra-2.1.11.jar:2.1.11]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [na:1.8.0_60]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [na:1.8.0_60]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]
> We are not able to know why cassandra is closing a socket that was close
> before. This is hapening mostly when cassandra is having high load of writes.
> Is it that a bug?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
