9114 really does nothing but confirm that 8880 is confusing. What you call a
log, I view as a metrics sink that writes to a log, but doesn’t actually use
any of configuration bits to configure a sink. That makes it a one-off, and
those tend to cause significant issues down the road.
At this p
HDFS-8880 does not require HDFS-9114. It is configured like any other logger by
adding '-Dnamenode.metrics.logger=DEBUG,NNMETRICSRFA' or equivalent to
HADOOP_NAMENODE_OPTS. Your concerns sound specific to 9114 and not inherent to
8880.
On 10/6/15, 1:28 PM, "Allen Wittenauer" wrote:
>
>As I m
Here are the design notes for Metrics V2 -
http://wiki.apache.org/hadoop/HADOOP-6728-MetricsV2
From: Andrew Wang
To: "hdfs-dev@hadoop.apache.org"
Sent: Tuesday, October 6, 2015 11:29 AM
Subject: Re: Questions on HDFS-8880
If it's duplicate we
As I mentioned in the original message, take a look at HDFS-9114, which is
basically making HDFS-8880 operable.
Generating a sink that is not a sink (which is what HDFS-8880 basically does),
isn’t particularly practical. 8880 would be much more appealing if it was a
sink. If FileSink isn’t fi
There is no property called hadoop.metrics.log.file. Where do you see it? And
there is no property that would show up in the command-line of every process.
namenode.metrics.logger would show up in the NN command-line and even that is
off by default.
FileSink looks limited for practical use.
- N
Current state is the custom stuff in HDFS-8880 is mostly undocumented except
for some tuning bits in hdfs-default.xml vs. the javadocs for metrics2.
Neither of which is ideal.
There’s no doubt the documentation for all of the metrics2 sinks are… sparse.
Which is likely what led to the duplica
If it's duplicate we should probably back it out, but taking a step back,
is the issue that there isn't good documentation about configuring Metrics2
/ FileSync? I see the API docs, but a user-focused guide on how to
configure Metrics2 would probably be a welcome addition.
HBase has a blog at http
Folks,
I’ve been looking over HDFS-8880 and it’s various follow-on JIRAs. The
intentions are good, but the implementation is mostly/effectively a duplicate
of the FileSink that’s already part of the Hadoop metrics subsystem. (which
therefore means it works with all daemons, out of the