You can file a bug for improving the error message if you like, though I don't think it's something we can do lightly, since it changes some behavior.
The frame size limit exists to let servers configure the maximum possible message size so that memory usage can be predicted and controlled. Making a multi-frame transport wouldn't really solve this problem. If you plan on having bigger messages, just increase the limit. On Sun, May 1, 2011 at 10:28 PM, Ross Black <[email protected]> wrote: > Hi, > > I am using the thrift client batch_mutate method with Cassandra 0.7.0 on > Ubuntu 10.10. > > When the size of the mutations gets too large, the client fails with the > following exception: > > Caused by: org.apache.thrift.transport. > TTransportException: java.net.SocketException: Connection reset > at > > org.apache.thrift.transport.TIOStreamTransport.write(TIOStreamTransport.java:147) > at > > org.apache.thrift.transport.TFramedTransport.flush(TFramedTransport.java:157) > at > > org.apache.cassandra.thrift.Cassandra$Client.send_batch_mutate(Cassandra.java:901) > at > > org.apache.cassandra.thrift.Cassandra$Client.batch_mutate(Cassandra.java:889) > at > > com.cxense.cxad.core.persistence.cassandra.store.BatchMutationTask.apply(BatchMutationTask.java:78) > at > > com.cxense.cxad.core.persistence.cassandra.store.BatchMutationTask.apply(BatchMutationTask.java:30) > at > > com.cxense.cassandra.conn.DefaultCassandraConnectionTemplate.execute(DefaultCassandraConnectionTemplate.java:316) > at > > com.cxense.cassandra.conn.DefaultCassandraConnectionTemplate.execute(DefaultCassandraConnectionTemplate.java:257) > at > > com.cxense.cxad.core.persistence.cassandra.store.AbstractCassandraStore.writeMutations(AbstractCassandraStore.java:492) > ... 39 more > Caused by: java.net.SocketException: Connection reset > at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:96) > at java.net.SocketOutputStream.write(SocketOutputStream.java:136) > at java.io.BufferedOutputStream.write(BufferedOutputStream.java:105) > at > > org.apache.thrift.transport.TIOStreamTransport.write(TIOStreamTransport.java:145) > ... 47 more > > > It took a while for me to discover that this error message was actually > result of the thrift message exceeding the maximum frame size specified for > the Cassandra server. (default 15MB) > [Using TFastFramedTransport with a max frame size of 15728640 bytes.] > > The error message looks to me like it is caused by a bug in Thrift server > code that assumes that any transport exception is a connection failure > which > should drop the connection. > Should this be raised as a bug against Thrift? > > From a client perspective it is extremely awkward to break a large request > into multiple smaller requests so that the max message size is not > exceeded. > Are there any plans for Thrift to fragment messages larger than a specified > size into multiple messages? > > > Thanks, > Ross >
