cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From K F <>
Subject sstableloader in version 2.0.14 doesn't honor thrift_framed_transport_size_in_mb set on server side
Date Fri, 14 Aug 2015 16:27:52 GMT
While using sstableloader in 2.0.14 we have discovered that setting the thrift_framed_transport_size_in_mb
to 16 in cassandra.yaml doesn't honor it. Did anybody see similar issue?
So, this is the exception seen,
org.apache.thrift.transport.TTransportException: Frame size (16165888) larger than max length
(15728640)!java.lang.RuntimeException: Could not retrieve endpoint ranges:         at$ExternalClient.init(       
at by: org.apache.thrift.transport.TTransportException:
Frame size (16165888) larger than max length (15728640)!        at org.apache.thrift.transport.TFramedTransport.readFrame( 
      at org.apache.thrift.transport.TTransport.readAll(       
at org.apache.thrift.protocol.TBinaryProtocol.readAll(       
at org.apache.thrift.protocol.TBinaryProtocol.readI32(       
at org.apache.thrift.protocol.TBinaryProtocol.readMessageBegin( 
      at org.apache.thrift.TServiceClient.receiveBase(       
at org.apache.cassandra.thrift.Cassandra$Client.recv_describe_ring( 
      at org.apache.cassandra.thrift.Cassandra$Client.describe_ring( 
      ... 2 more
On Server side, it's the following.
2015-08-14 15:10:10,637 [main] INFO ThriftServer Using TFramedTransport with a max frame size
of 16777216 bytes.

View raw message