[ 
https://issues.apache.org/jira/browse/HBASE-14451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15049340#comment-15049340
 ] 

stack edited comment on HBASE-14451 at 12/10/15 12:53 AM:
----------------------------------------------------------

Giving up on this for the moment. I am not sending traces so need to do more 
debug. Fixed a bunch of NPEs because there was not tracer in the particular 
context but it doesn't seem like we are generating any spans at the moment post 
redo to fit the htrace-4 semantic.

I was running with htrace DEBUG on and with following config:

{code}
 24      <property>
 25      <name>hbase.htrace.span.receiver.classes</name>
 26      <value>org.apache.htrace.impl.HTracedSpanReceiver</value>
 27      <description>
 28      The class name of the HTrace SpanReceivers to use inside
 29      HBase. If there are no class names supplied here, tracings will not
 30     be emitted.
 31      </description>
 32      </property>
 33      <property>
 34        <name>
 35          hbase.htrace.htraced.receiver.address
 36        </name>
 37        <value>localhost:9075</value>
 38      </property>
 39      <property>
 40        <name>
 41      hbase.htraced.error.log.period.ms
 42        </name>
 43        <value>1000</value>
 44      </property>
 45      <property>
 46      <name>hbase.htrace.sampler.classes</name>
 47      <value>org.apache.htrace.core.AlwaysSampler</value>
 48      <description>Sampler to use when tracing. Default is
 49      org.apache.htrace.core.NeverSampler. Other options are
 50      org.apache.htrace.core.AlwaysSampler and
 51      org.apache.htrace.core.ProbabilitySampler. See htrace-core
 52      for options provided by htrace.
 53      </description>
 54      </property>
{code}

Attached is latest patch.


was (Author: stack):
Giving up on this for the moment. I am not sending traces so need to do more 
debug. Fixed a bunch of NPEs because there was not tracer in the particular 
context but it doesn't seem like we are generating any spans at the moment post 
redo to fit the htrace-4 semantic.

I was running with htrace DEBUG on and with following config:

{code}
+     <property>
+     <name>hbase.htrace.htraced.span.receiver.classes</name>
+     <value>org.apache.htrace.impl.HTracedSpanReceiver</value>
+     <description>
+     The class name of the HTrace SpanReceivers to use inside
+     HBase. If there are no class names supplied here, tracings will not be 
emitted.
+     </description>
+     </property>
+     <property>
+       <name>
+         hbase.htrace.htraced.receiver.address
+       </name>
+       <property>
+         localhost:9075
+       </property>
+     </property>
+     <property>
+       <name>
+     hbase.htraced.error.log.period.ms
+       </name>
+       <property>
+         1000
+       </property>
+     </property>
+     <property>
+     <name>hbase.htrace.sampler.classes</name>
+     <value>org.apache.htrace.core.AlwaysSampler</value>
+     <description>Sampler to use when tracing. Default is
+     org.apache.htrace.core.NeverSampler. Other options are
+     org.apache.htrace.core.AlwaysSampler and
+     org.apache.htrace.core.ProbabilitySampler. See htrace-core
+     for options provided by htrace.
+     </description>
+     </property>
{code}

Attached is latest patch.

> Move on to htrace-4.0.1 (from htrace-3.2.0)
> -------------------------------------------
>
>                 Key: HBASE-14451
>                 URL: https://issues.apache.org/jira/browse/HBASE-14451
>             Project: HBase
>          Issue Type: Task
>            Reporter: stack
>            Assignee: stack
>         Attachments: 14451.txt, 14451.v10.txt, 14451.v10.txt, 14451v11.patch, 
> 14451v13.txt, 14451v2.txt, 14451v3.txt, 14451v4.txt, 14451v5.txt, 
> 14451v6.txt, 14451v7.txt, 14451v8.txt, 14451v9.txt, 14551v12.patch
>
>
> htrace-4.0.0 was just release with a new API. Get up on it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to