phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-1226) Exception in Tracing
Date Tue, 02 Sep 2014 19:24:20 GMT


James Taylor commented on PHOENIX-1226:

My idea was to always encode the data written to the sink as strings. Is that what is done
today for the metrics written out by HBase? Then use the key to lookup the column in the Phoenix
tracing table. If found, then translate the string to the type of the column. If not, store
the value as a string. No need then to prefix the key with 'phoenix' or encode the type in
the key. It'd just be a general way of _typing_ the trace data.

> Exception in Tracing
> --------------------
>                 Key: PHOENIX-1226
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.1
>         Environment: 0.98.5 hbase, 4.1.0 phoenix
>            Reporter: Dan Di Spaltro
>            Assignee: Jesse Yates
>         Attachments: phoenix-1226-4.0-v0.patch, phoenix-1226-4.0-v1.patch
> I was exposed to an exception in the tracing code, during my test setup of Phoenix in
the following code:
> {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
> 	at org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(
> 	at org.apache.hadoop.hbase.ipc.RpcExecutor$
> 	at
> {code}
> 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