We had this issue when using hive on cassandra.
We had to replace the thrift jar with our own patches.

On Fri, Aug 14, 2015 at 5:27 PM, K F <kf200...@yahoo.com> wrote:

> 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
> org.apache.cassandra.tools.BulkLoader$ExternalClient.init(BulkLoader.java:282)
>         at
> org.apache.cassandra.io.sstable.SSTableLoader.stream(SSTableLoader.java:149)
>         at org.apache.cassandra.tools.BulkLoader.main(BulkLoader.java:94)
> Caused by: org.apache.thrift.transport.TTransportException: Frame size
> (16165888) larger than max length (15728640)!
>         at
> org.apache.thrift.transport.TFramedTransport.readFrame(TFramedTransport.java:137)
>         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:362)
>         at
> org.apache.thrift.protocol.TBinaryProtocol.readI32(TBinaryProtocol.java:284)
>         at
> org.apache.thrift.protocol.TBinaryProtocol.readMessageBegin(TBinaryProtocol.java:191)
>         at
> org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:69)
>         at
> org.apache.cassandra.thrift.Cassandra$Client.recv_describe_ring(Cassandra.java:1251)
>         at
> org.apache.cassandra.thrift.Cassandra$Client.describe_ring(Cassandra.java:1238)
>         at
> org.apache.cassandra.tools.BulkLoader$ExternalClient.init(BulkLoader.java:258)
>         ... 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.
>
>

Reply via email to