[
https://issues.apache.org/jira/browse/HADOOP-7311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038332#comment-13038332
]
Luke Lu commented on HADOOP-7311:
---------------------------------
bq. Luke, I don't know how you can make decisions based only on one comment.
Well, it was approved by Y dev/ops, of course :). The post was sent to both
general and common-dev. People have many weeks to voice their opinions. The
main consumers of the metrics system are ops and perf guys. I guess that they
don't have strong opinions on how it should work as long as it can be easily
made to work. I'm sure that you heard of lazy consensus.
bq. I don't think Gary (the only one who cared) would be happy with the
solution, when he sees it, as he was asking for "a phased transition" to
metrics2 for HBase.
#2 the OP clearly outlined the pros and cons of the approach. HBase will
continue sending their specific metrics with metrics1 and Hadoop (common, hdfs,
mapreduce) will send hadoop framework metrics with metrics2. i.e., in the
transition period, ops would need to configure both hadoop-metrics.properties
for HBase and hadoop-metrics2.properties for Hadoop. It's a working solution
for the transition period.
bq. Could you please elaborate or post links on how to get metrics2 run. We use
Ganglia.
The syntax to configure a consumer/sink for metrics (in the
hadoop-metrics2.properties):
{noformat}
[service-name].sink.[sink-name].[option]=value
{noformat}
Some examples are included in the trunk conf/hadoop-metrics2.properties for
common and hdfs, as well as the [configuration
section|http://wiki.apache.org/hadoop/HADOOP-6728-MetricsV2#Configuration] of
the [design doc|http://wiki.apache.org/hadoop/HADOOP-6728-MetricsV2].
An example of metrics2 config using ganglia (3.0.x or 3.1.x?) would be:
{noformat}
*.ganglia.class=org.apache.hadoop.metrics2.sink.ganglia.Ganglia31
*.period=10
namenode.sink.ganglia.address=localhost:8649
jobtracker.sink.ganglia.address=localhost:8649
tasktracker.sink.ganglia.address=localhost:8649
{noformat}
Of course, the org.apache.hadoop.metrics2.sink.ganglia.* classes don't exist
yet. We'll have to implement them (sink examples can be found in the FileSink
or the EchoPlugin in the design doc.).
> Port remaining metrics v1 from trunk to branch-0.20-security
> ------------------------------------------------------------
>
> Key: HADOOP-7311
> URL: https://issues.apache.org/jira/browse/HADOOP-7311
> Project: Hadoop Common
> Issue Type: Bug
> Components: metrics
> Affects Versions: 0.20.203.0
> Reporter: Konstantin Shvachko
> Assignee: Konstantin Shvachko
> Fix For: 0.20.204.0
>
> Attachments: metrics-0.20-security.patch
>
>
> HADOOP-7190 added metrics packages/classes. This is a port from trunk to make
> them actually work for the security branch.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
