phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Di Spaltro (JIRA)" <>
Subject [jira] [Created] (PHOENIX-1226) Exception in Tracing
Date Mon, 01 Sep 2014 02:29:20 GMT
Dan Di Spaltro created PHOENIX-1226:

             Summary: Exception in Tracing
                 Key: PHOENIX-1226
             Project: Phoenix
          Issue Type: Bug
    Affects Versions: 4.1
         Environment: 0.98.5 hbase, 4.1.0 phoenix
            Reporter: Dan Di Spaltro

I was exposed to an exception in the tracing code, during my test setup of Phoenix in the
following code:

58062 [defaultRpcServer.handler=2,queue=0,port=53950] WARN  org.apache.hadoop.ipc.RpcServer
 - defaultRpcServer.handler=2,queue=0,port=53950: caught: java.lang.IllegalArgumentException:
offset (0) + length (4) exceed the capacity of the array: 3
	at org.apache.hadoop.hbase.util.Bytes.explainWrongLengthOrOffset(
	at org.apache.hadoop.hbase.util.Bytes.toInt(
	at org.apache.hadoop.hbase.util.Bytes.toInt(
	at org.apache.phoenix.trace.TracingCompat.readAnnotation(
	at org.apache.phoenix.trace.TraceMetricSource.receiveSpan(
	at org.cloudera.htrace.Tracer.deliver(
	at org.cloudera.htrace.impl.MilliSpan.stop(
	at org.cloudera.htrace.TraceScope.close(
	at org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(
	at org.apache.hadoop.hbase.ipc.RpcExecutor$

It is related to the following line of code where we interpret all KV annotation values as
byte-wise integers here:

Here is where HBase is adding a non-integer KV annotation:

The fix should be simple, but I am not aware of all the related issues in changing this.

cc [~jesse_yates], [], [~giacomotaylor]

This message was sent by Atlassian JIRA

View raw message