incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lanny Ripple <>
Subject Thrift message length exceeded
Date Tue, 09 Apr 2013 15:16:54 GMT

We have recently upgraded to Cass 1.2.3 from Cass 1.1.5.  We ran sstableupgrades and got the
ring on its feet and we are now seeing a new issue.

When we run MapReduce jobs against practically any table we find the following errors:

2013-04-09 09:58:47,746 INFO org.apache.hadoop.util.NativeCodeLoader: Loaded the native-hadoop
2013-04-09 09:58:47,899 INFO org.apache.hadoop.metrics.jvm.JvmMetrics: Initializing JVM Metrics
with processName=MAP, sessionId=
2013-04-09 09:58:48,021 INFO org.apache.hadoop.util.ProcessTree: setsid exited with exit code
2013-04-09 09:58:48,024 INFO org.apache.hadoop.mapred.Task:  Using ResourceCalculatorPlugin
: org.apache.hadoop.util.LinuxResourceCalculatorPlugin@4a48edb5
2013-04-09 09:58:50,475 INFO org.apache.hadoop.mapred.TaskLogsTruncater: Initializing logs'
truncater with mapRetainSize=-1 and reduceRetainSize=-1
2013-04-09 09:58:50,477 WARN org.apache.hadoop.mapred.Child: Error running child
java.lang.RuntimeException: org.apache.thrift.TException: Message length exceeded: 106
	at org.apache.cassandra.hadoop.ColumnFamilyRecordReader$StaticRowIterator.maybeInit(
	at org.apache.cassandra.hadoop.ColumnFamilyRecordReader$StaticRowIterator.computeNext(
	at org.apache.cassandra.hadoop.ColumnFamilyRecordReader$StaticRowIterator.computeNext(
	at org.apache.cassandra.hadoop.ColumnFamilyRecordReader.getProgress(
	at org.apache.hadoop.mapred.MapTask$NewTrackingRecordReader.getProgress(
	at org.apache.hadoop.mapred.MapTask$NewTrackingRecordReader.nextKeyValue(
	at org.apache.hadoop.mapreduce.MapContext.nextKeyValue(
	at org.apache.hadoop.mapred.MapTask.runNewMapper(
	at org.apache.hadoop.mapred.Child$
	at Method)
	at org.apache.hadoop.mapred.Child.main(
Caused by: org.apache.thrift.TException: Message length exceeded: 106
	at org.apache.thrift.protocol.TBinaryProtocol.checkReadLength(
	at org.apache.thrift.protocol.TBinaryProtocol.readBinary(
	at org.apache.cassandra.thrift.Cassandra$
	at org.apache.thrift.TServiceClient.receiveBase(
	at org.apache.cassandra.thrift.Cassandra$Client.recv_get_range_slices(
	at org.apache.cassandra.thrift.Cassandra$Client.get_range_slices(
	at org.apache.cassandra.hadoop.ColumnFamilyRecordReader$StaticRowIterator.maybeInit(
	... 16 more
2013-04-09 09:58:50,481 INFO org.apache.hadoop.mapred.Task: Runnning cleanup for the task

The message length listed on each failed job differs (not always 106).  Jobs that used to
run fine now fail with code compiled against cass 1.2.3 (and work fine if compiled against
1.1.5 and run against the 1.2.3 servers in production).  I'm using the following setup to
configure the job:

  def cassConfig(job: Job) {
    val conf = job.getConfiguration()

    ConfigHelper.setInputRpcPort(conf, "" + 9160)
    ConfigHelper.setInputInitialAddress(conf, Config.hostip)

    ConfigHelper.setInputPartitioner(conf, "org.apache.cassandra.dht.RandomPartitioner")
    ConfigHelper.setInputColumnFamily(conf, Config.keyspace, Config.cfname)

    val pred = {
      val range = new SliceRange()
        .setCount(4096 * 1000)

      new SlicePredicate().setSlice_range(range)

    ConfigHelper.setInputSlicePredicate(conf, pred)

The job consists only of a mapper that increments counters for each row and associated columns
so all I'm really doing is exercising ColumnFamilyRecordReader.

Has anyone else seen this?  Is there a workaround/fix to get our jobs running?

View raw message