Michael Kjellman created CASSANDRA-4922:
-------------------------------------------

             Summary: TTransportException thrown many times 
                 Key: CASSANDRA-4922
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4922
             Project: Cassandra
          Issue Type: Bug
          Components: Hadoop
    Affects Versions: 1.2.0 beta 1
         Environment: setup log4j to log DEBUG warnings, hadoop 1.0.3, 3 node 
dev cluster rf=3
            Reporter: Michael Kjellman


I'm seeing a ton of these st's when either Streaming into Cassandra with BOF or 
reading with ColumnFamilyInputFormat.

DEBUG [Thrift:16] 2012-11-06 11:18:27,933 CustomTThreadPoolServer.java (line 
210) Thrift transport error occurred during processing of message.
org.apache.thrift.transport.TTransportException
        at 
org.apache.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:132)
        at org.apache.thrift.transport.TTransport.readAll(TTransport.java:84)
        at 
org.apache.thrift.transport.TFramedTransport.readFrame(TFramedTransport.java:129)
        at 
org.apache.thrift.transport.TFramedTransport.read(TFramedTransport.java:101)
        at org.apache.thrift.transport.TTransport.readAll(TTransport.java:84)
        at 
org.apache.thrift.protocol.TBinaryProtocol.readAll(TBinaryProtocol.java:378)
        at 
org.apache.thrift.protocol.TBinaryProtocol.readI32(TBinaryProtocol.java:297)
        at 
org.apache.thrift.protocol.TBinaryProtocol.readMessageBegin(TBinaryProtocol.java:204)
        at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:22)
        at 
org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run(CustomTThreadPoolServer.java:200)
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
        at java.lang.Thread.run(Thread.java:722)
 

--
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

Reply via email to