You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@phoenix.apache.org by ashish tapdiya <as...@gmail.com> on 2015/04/02 22:53:15 UTC
Phoenix tracing
Hi,
I am trying to setup tracing following the steps specified on the Phoenix
webpage,
http://phoenix.apache.org/tracing.html
Below are the steps I have followed,
1. On the client, property files (hadoop-metrics2-phoenix.properties and
hadoop-metrics2-hbase.properties) came configured with the distribution
and are on the classpath.
2. On the server nodes (master + slaves), appended following to the
/usr/lib/hbase/conf/hadoop-metrics2-hbase.properties file,
# ensure that we receive traces on the server
hbase.sink.tracing.class=org.apache.phoenix.trace.PhoenixMetricsSink
# Tell the sink where to write the metrics
hbase.sink.tracing.writer-class=org.apache.phoenix.trace.PhoenixTableMetricsWriter
# Only handle traces with a context of "tracing"
hbase.sink.tracing.context=tracing
3. Added the following property to the client's hbase-site.xml
<configuration>
<property>
<name>phoenix.trace.frequency</name>
<value>always</value>
</property>
</configuration>
4. Created the SYSTEM.TRACING_STATS table using,
CREATE TABLE *SYSTEM.TRACING_STATS* (
*trace_id* BIGINT NOT NULL,
*parent_id* BIGINT NOT NULL,
*span_id* BIGINT NOT NULL,
*description* VARCHAR,
*start_time* BIGINT,
*end_time* BIGINT,
*hostname* VARCHAR,
*tags.count* SMALLINT,
*annotations.count* SMALLINT,
CONSTRAINT pk PRIMARY KEY (*trace_id, parent_id, span_id*)
5. Restarted cluster
However, after running queries from the client, SYSTEM.TRACING_STATS
table returns 0 rows.
I am using cloudera distribution 5.3.2 with
Hadoop Ver: 2.5.0
HBase Ver: 0.98.6
Phoenix Ver: 4.3.0
Thanks,
~Ashish
Re: Re: Phoenix tracing
Posted by Jesse Yates <je...@gmail.com>.
It looks like you are using two different metrics files on the classpath of
the server. You can only have one (quirk of Hadoop's metrics2 system). The
configurations for the phoenix sinks should be in the
hadoop-metrics2-hbase.properties
file since HBase will load the metrics system before the phoenix CPs have a
chance to initialize it.
See "hadoop-metrics2-hbase.properties" under
http://phoenix.apache.org/tracing.html for what should go into the file for
phoenix tracing to be enabled.
On Fri, Apr 3, 2015 at 12:43 PM ashish tapdiya <as...@gmail.com>
wrote:
> Hi,
>
> In one slave node's region-server logs i see
>
> 2015-04-03 14:07:47,162 INFO org.apache.phoenix.metrics.Metrics:
> Initializing metrics system: phoenix
> 2015-04-03 14:07:47,162 WARN
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl: HBase metrics system
> already initialized!
> 2015-04-03 14:07:47,163 WARN org.apache.phoenix.metrics.Metrics: Phoenix
> metrics2/tracing sink was not started. Should be it be?
>
> On Master and other slaves i dont see phoenix metrics but only hbase
> metrics initialization
>
> 2015-04-03 14:07:22,275 INFO
> org.apache.hadoop.metrics2.impl.MetricsConfig: loaded properties from
> hadoop-metrics2.properties
> 2015-04-03 14:07:22,338 INFO
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl: Scheduled snapshot
> period at 10 second(s).
> 2015-04-03 14:07:22,339 INFO
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl: HBase metrics system
> started
>
> Thanks,
> ~Ashish
>
>
> On Thu, Apr 2, 2015 at 8:43 PM, Fulin Sun <su...@certusnet.com.cn> wrote:
>
>> Hi, there
>>
>> In your regionserver side logs, can you find something related with
>> phoenix tracing ?
>> If not, I assume you still had configs wrong placed.
>>
>> Thanks,
>> Sun.
>>
>> ------------------------------
>> ------------------------------
>>
>> CertusNet
>>
>>
>> *From:* ashish tapdiya <as...@gmail.com>
>> *Date:* 2015-04-03 09:38
>> *To:* user <us...@phoenix.apache.org>
>> *Subject:* Re: Phoenix tracing
>> Hi Sun,
>>
>> hbase-site.xml is already in bin directory and the directory is on
>> classpath
>>
>> Thanks,
>> ~Ashish
>>
>> On Thu, Apr 2, 2015 at 8:13 PM, Fulin Sun <su...@certusnet.com.cn> wrote:
>>
>>> Hi,
>>>
>>> Maybe you want to put your client side hbase-site.xml into phoenix bin
>>> directory.
>>>
>>> I once encountered such problem and doing that just resolved it.
>>>
>>> Thanks,
>>> Sun.
>>>
>>> ------------------------------
>>> ------------------------------
>>>
>>> CertusNet
>>>
>>>
>>> *From:* ashish tapdiya <as...@gmail.com>
>>> *Date:* 2015-04-03 04:53
>>> *To:* user <us...@phoenix.apache.org>
>>> *Subject:* Phoenix tracing
>>> Hi,
>>>
>>> I am trying to setup tracing following the steps specified on the
>>> Phoenix webpage,
>>> http://phoenix.apache.org/tracing.html
>>>
>>> Below are the steps I have followed,
>>>
>>> 1. On the client, property files (hadoop-metrics2-phoenix.properties and
>>> hadoop-metrics2-hbase.properties) came configured with the distribution
>>> and are on the classpath.
>>>
>>> 2. On the server nodes (master + slaves), appended following to the
>>> /usr/lib/hbase/conf/hadoop-metrics2-hbase.properties file,
>>>
>>> # ensure that we receive traces on the server
>>> hbase.sink.tracing.class=org.apache.phoenix.trace.PhoenixMetricsSink
>>> # Tell the sink where to write the metrics
>>> hbase.sink.tracing.writer-class=org.apache.phoenix.trace.PhoenixTableMetricsWriter
>>> # Only handle traces with a context of "tracing"
>>> hbase.sink.tracing.context=tracing
>>>
>>> 3. Added the following property to the client's hbase-site.xml
>>> <configuration>
>>> <property>
>>> <name>phoenix.trace.frequency</name>
>>> <value>always</value>
>>> </property>
>>> </configuration>
>>>
>>> 4. Created the SYSTEM.TRACING_STATS table using,
>>>
>>> CREATE TABLE *SYSTEM.TRACING_STATS* (
>>> *trace_id* BIGINT NOT NULL,
>>> *parent_id* BIGINT NOT NULL,
>>> *span_id* BIGINT NOT NULL,
>>> *description* VARCHAR,
>>> *start_time* BIGINT,
>>> *end_time* BIGINT,
>>> *hostname* VARCHAR,
>>> *tags.count* SMALLINT,
>>> *annotations.count* SMALLINT,
>>> CONSTRAINT pk PRIMARY KEY (*trace_id, parent_id, span_id*)
>>>
>>> 5. Restarted cluster
>>>
>>> However, after running queries from the client, SYSTEM.TRACING_STATS table returns 0 rows.
>>>
>>>
>>> I am using cloudera distribution 5.3.2 with
>>>
>>> Hadoop Ver: 2.5.0
>>> HBase Ver: 0.98.6
>>>
>>> Phoenix Ver: 4.3.0
>>>
>>> Thanks,
>>> ~Ashish
>>>
>>>
>>>
>>
>
Re: Re: Phoenix tracing
Posted by ashish tapdiya <as...@gmail.com>.
Hi,
In one slave node's region-server logs i see
2015-04-03 14:07:47,162 INFO org.apache.phoenix.metrics.Metrics:
Initializing metrics system: phoenix
2015-04-03 14:07:47,162 WARN
org.apache.hadoop.metrics2.impl.MetricsSystemImpl: HBase metrics system
already initialized!
2015-04-03 14:07:47,163 WARN org.apache.phoenix.metrics.Metrics: Phoenix
metrics2/tracing sink was not started. Should be it be?
On Master and other slaves i dont see phoenix metrics but only hbase
metrics initialization
2015-04-03 14:07:22,275 INFO org.apache.hadoop.metrics2.impl.MetricsConfig:
loaded properties from hadoop-metrics2.properties
2015-04-03 14:07:22,338 INFO
org.apache.hadoop.metrics2.impl.MetricsSystemImpl: Scheduled snapshot
period at 10 second(s).
2015-04-03 14:07:22,339 INFO
org.apache.hadoop.metrics2.impl.MetricsSystemImpl: HBase metrics system
started
Thanks,
~Ashish
On Thu, Apr 2, 2015 at 8:43 PM, Fulin Sun <su...@certusnet.com.cn> wrote:
> Hi, there
>
> In your regionserver side logs, can you find something related with
> phoenix tracing ?
> If not, I assume you still had configs wrong placed.
>
> Thanks,
> Sun.
>
> ------------------------------
> ------------------------------
>
> CertusNet
>
>
> *From:* ashish tapdiya <as...@gmail.com>
> *Date:* 2015-04-03 09:38
> *To:* user <us...@phoenix.apache.org>
> *Subject:* Re: Phoenix tracing
> Hi Sun,
>
> hbase-site.xml is already in bin directory and the directory is on
> classpath
>
> Thanks,
> ~Ashish
>
> On Thu, Apr 2, 2015 at 8:13 PM, Fulin Sun <su...@certusnet.com.cn> wrote:
>
>> Hi,
>>
>> Maybe you want to put your client side hbase-site.xml into phoenix bin
>> directory.
>>
>> I once encountered such problem and doing that just resolved it.
>>
>> Thanks,
>> Sun.
>>
>> ------------------------------
>> ------------------------------
>>
>> CertusNet
>>
>>
>> *From:* ashish tapdiya <as...@gmail.com>
>> *Date:* 2015-04-03 04:53
>> *To:* user <us...@phoenix.apache.org>
>> *Subject:* Phoenix tracing
>> Hi,
>>
>> I am trying to setup tracing following the steps specified on the Phoenix
>> webpage,
>> http://phoenix.apache.org/tracing.html
>>
>> Below are the steps I have followed,
>>
>> 1. On the client, property files (hadoop-metrics2-phoenix.properties and
>> hadoop-metrics2-hbase.properties) came configured with the distribution
>> and are on the classpath.
>>
>> 2. On the server nodes (master + slaves), appended following to the
>> /usr/lib/hbase/conf/hadoop-metrics2-hbase.properties file,
>>
>> # ensure that we receive traces on the server
>> hbase.sink.tracing.class=org.apache.phoenix.trace.PhoenixMetricsSink
>> # Tell the sink where to write the metrics
>> hbase.sink.tracing.writer-class=org.apache.phoenix.trace.PhoenixTableMetricsWriter
>> # Only handle traces with a context of "tracing"
>> hbase.sink.tracing.context=tracing
>>
>> 3. Added the following property to the client's hbase-site.xml
>> <configuration>
>> <property>
>> <name>phoenix.trace.frequency</name>
>> <value>always</value>
>> </property>
>> </configuration>
>>
>> 4. Created the SYSTEM.TRACING_STATS table using,
>>
>> CREATE TABLE *SYSTEM.TRACING_STATS* (
>> *trace_id* BIGINT NOT NULL,
>> *parent_id* BIGINT NOT NULL,
>> *span_id* BIGINT NOT NULL,
>> *description* VARCHAR,
>> *start_time* BIGINT,
>> *end_time* BIGINT,
>> *hostname* VARCHAR,
>> *tags.count* SMALLINT,
>> *annotations.count* SMALLINT,
>> CONSTRAINT pk PRIMARY KEY (*trace_id, parent_id, span_id*)
>>
>> 5. Restarted cluster
>>
>> However, after running queries from the client, SYSTEM.TRACING_STATS table returns 0 rows.
>>
>>
>> I am using cloudera distribution 5.3.2 with
>>
>> Hadoop Ver: 2.5.0
>> HBase Ver: 0.98.6
>>
>> Phoenix Ver: 4.3.0
>>
>> Thanks,
>> ~Ashish
>>
>>
>>
>
Re: Re: Phoenix tracing
Posted by Fulin Sun <su...@certusnet.com.cn>.
Hi, there
In your regionserver side logs, can you find something related with phoenix tracing ?
If not, I assume you still had configs wrong placed.
Thanks,
Sun.
CertusNet
From: ashish tapdiya
Date: 2015-04-03 09:38
To: user
Subject: Re: Phoenix tracing
Hi Sun,
hbase-site.xml is already in bin directory and the directory is on classpath
Thanks,
~Ashish
On Thu, Apr 2, 2015 at 8:13 PM, Fulin Sun <su...@certusnet.com.cn> wrote:
Hi,
Maybe you want to put your client side hbase-site.xml into phoenix bin directory.
I once encountered such problem and doing that just resolved it.
Thanks,
Sun.
CertusNet
From: ashish tapdiya
Date: 2015-04-03 04:53
To: user
Subject: Phoenix tracing
Hi,
I am trying to setup tracing following the steps specified on the Phoenix webpage,
http://phoenix.apache.org/tracing.html
Below are the steps I have followed,
1. On the client, property files (hadoop-metrics2-phoenix.properties and hadoop-metrics2-hbase.properties) came configured with the distribution and are on the classpath.
2. On the server nodes (master + slaves), appended following to the /usr/lib/hbase/conf/hadoop-metrics2-hbase.properties file,
# ensure that we receive traces on the server
hbase.sink.tracing.class=org.apache.phoenix.trace.PhoenixMetricsSink
# Tell the sink where to write the metrics
hbase.sink.tracing.writer-class=org.apache.phoenix.trace.PhoenixTableMetricsWriter
# Only handle traces with a context of "tracing"
hbase.sink.tracing.context=tracing
3. Added the following property to the client's hbase-site.xml
<configuration>
<property>
<name>phoenix.trace.frequency</name>
<value>always</value>
</property>
</configuration>
4. Created the SYSTEM.TRACING_STATS table using,
CREATE TABLE SYSTEM.TRACING_STATS (
trace_id BIGINT NOT NULL,
parent_id BIGINT NOT NULL,
span_id BIGINT NOT NULL,
description VARCHAR,
start_time BIGINT,
end_time BIGINT,
hostname VARCHAR,
tags.count SMALLINT,
annotations.count SMALLINT,
CONSTRAINT pk PRIMARY KEY (trace_id, parent_id, span_id)
5. Restarted cluster However, after running queries from the client, SYSTEM.TRACING_STATS table returns 0 rows.
I am using cloudera distribution 5.3.2 with
Hadoop Ver: 2.5.0
HBase Ver: 0.98.6
Phoenix Ver: 4.3.0
Thanks,
~Ashish
Re: Phoenix tracing
Posted by ashish tapdiya <as...@gmail.com>.
Hi Sun,
hbase-site.xml is already in bin directory and the directory is on classpath
Thanks,
~Ashish
On Thu, Apr 2, 2015 at 8:13 PM, Fulin Sun <su...@certusnet.com.cn> wrote:
> Hi,
>
> Maybe you want to put your client side hbase-site.xml into phoenix bin
> directory.
>
> I once encountered such problem and doing that just resolved it.
>
> Thanks,
> Sun.
>
> ------------------------------
> ------------------------------
>
> CertusNet
>
>
> *From:* ashish tapdiya <as...@gmail.com>
> *Date:* 2015-04-03 04:53
> *To:* user <us...@phoenix.apache.org>
> *Subject:* Phoenix tracing
> Hi,
>
> I am trying to setup tracing following the steps specified on the Phoenix
> webpage,
> http://phoenix.apache.org/tracing.html
>
> Below are the steps I have followed,
>
> 1. On the client, property files (hadoop-metrics2-phoenix.properties and
> hadoop-metrics2-hbase.properties) came configured with the distribution
> and are on the classpath.
>
> 2. On the server nodes (master + slaves), appended following to the
> /usr/lib/hbase/conf/hadoop-metrics2-hbase.properties file,
>
> # ensure that we receive traces on the server
> hbase.sink.tracing.class=org.apache.phoenix.trace.PhoenixMetricsSink
> # Tell the sink where to write the metrics
> hbase.sink.tracing.writer-class=org.apache.phoenix.trace.PhoenixTableMetricsWriter
> # Only handle traces with a context of "tracing"
> hbase.sink.tracing.context=tracing
>
> 3. Added the following property to the client's hbase-site.xml
> <configuration>
> <property>
> <name>phoenix.trace.frequency</name>
> <value>always</value>
> </property>
> </configuration>
>
> 4. Created the SYSTEM.TRACING_STATS table using,
>
> CREATE TABLE *SYSTEM.TRACING_STATS* (
> *trace_id* BIGINT NOT NULL,
> *parent_id* BIGINT NOT NULL,
> *span_id* BIGINT NOT NULL,
> *description* VARCHAR,
> *start_time* BIGINT,
> *end_time* BIGINT,
> *hostname* VARCHAR,
> *tags.count* SMALLINT,
> *annotations.count* SMALLINT,
> CONSTRAINT pk PRIMARY KEY (*trace_id, parent_id, span_id*)
>
> 5. Restarted cluster
>
> However, after running queries from the client, SYSTEM.TRACING_STATS table returns 0 rows.
>
>
> I am using cloudera distribution 5.3.2 with
>
> Hadoop Ver: 2.5.0
> HBase Ver: 0.98.6
>
> Phoenix Ver: 4.3.0
>
> Thanks,
> ~Ashish
>
>
>
Re: Phoenix tracing
Posted by Fulin Sun <su...@certusnet.com.cn>.
Hi,
Maybe you want to put your client side hbase-site.xml into phoenix bin directory.
I once encountered such problem and doing that just resolved it.
Thanks,
Sun.
CertusNet
From: ashish tapdiya
Date: 2015-04-03 04:53
To: user
Subject: Phoenix tracing
Hi,
I am trying to setup tracing following the steps specified on the Phoenix webpage,
http://phoenix.apache.org/tracing.html
Below are the steps I have followed,
1. On the client, property files (hadoop-metrics2-phoenix.properties and hadoop-metrics2-hbase.properties) came configured with the distribution and are on the classpath.
2. On the server nodes (master + slaves), appended following to the /usr/lib/hbase/conf/hadoop-metrics2-hbase.properties file,
# ensure that we receive traces on the server
hbase.sink.tracing.class=org.apache.phoenix.trace.PhoenixMetricsSink
# Tell the sink where to write the metrics
hbase.sink.tracing.writer-class=org.apache.phoenix.trace.PhoenixTableMetricsWriter
# Only handle traces with a context of "tracing"
hbase.sink.tracing.context=tracing
3. Added the following property to the client's hbase-site.xml
<configuration>
<property>
<name>phoenix.trace.frequency</name>
<value>always</value>
</property>
</configuration>
4. Created the SYSTEM.TRACING_STATS table using,
CREATE TABLE SYSTEM.TRACING_STATS (
trace_id BIGINT NOT NULL,
parent_id BIGINT NOT NULL,
span_id BIGINT NOT NULL,
description VARCHAR,
start_time BIGINT,
end_time BIGINT,
hostname VARCHAR,
tags.count SMALLINT,
annotations.count SMALLINT,
CONSTRAINT pk PRIMARY KEY (trace_id, parent_id, span_id)
5. Restarted cluster However, after running queries from the client, SYSTEM.TRACING_STATS table returns 0 rows.
I am using cloudera distribution 5.3.2 with
Hadoop Ver: 2.5.0
HBase Ver: 0.98.6
Phoenix Ver: 4.3.0
Thanks,
~Ashish