hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Mackrory (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-14475) Metrics of S3A don't print out when enable it in Hadoop metrics property file
Date Fri, 01 Dec 2017 20:16:00 GMT

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

Sean Mackrory commented on HADOOP-14475:
----------------------------------------

{quote} the test thinks s3guard is off, but it isn't, so the counters are wrong.{quote}

Ah that makes sense. Looks like it checks that there actually is a metadatastore, though.
It's not naively checking a specific config property. So that shouldn't be an issue we need
to fix.

{quote}The important thing is just to acquire the locks in the same order everywhere.{quote}

Well there's only one lock being acquired here, and it's only in testing, and initialization
/ closing, so perf is not a primary concern. That has highlighted another goof to me, though:
these accesses needs to be synchronized across all instances, not just the one instance. Can't
synchronize against the static MetricsSystem instance itself, so I'll just synchronize against
a static object dedicated to that purpose. I'll attach another patch shortly...

> Metrics of S3A don't print out  when enable it in Hadoop metrics property file
> ------------------------------------------------------------------------------
>
>                 Key: HADOOP-14475
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14475
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 2.8.0
>         Environment: uname -a
> Linux client01 4.4.0-74-generic #95-Ubuntu SMP Wed Apr 12 09:50:34 UTC 2017 x86_64 x86_64
x86_64 GNU/Linux
>  cat /etc/issue
> Ubuntu 16.04.2 LTS \n \l
>            Reporter: Yonger
>            Assignee: Yonger
>         Attachments: HADOOP-14475-003.patch, HADOOP-14475.002.patch, HADOOP-14475.005.patch,
HADOOP-14475.006.patch, HADOOP-14475.008.patch, HADOOP-14475.009.patch, HADOOP-14475.010.patch,
HADOOP-14475.011.patch, HADOOP-14475.012.patch, HADOOP-14475.013.patch, HADOOP-14475.014.patch,
HADOOP-14475.015.patch, HADOOP-14475.016.patch, HADOOP-14775.007.patch, failsafe-report-s3a-it.html,
failsafe-report-s3a-scale.html, failsafe-report-scale.html, failsafe-report-scale.zip, s3a-metrics.patch1,
stdout.zip
>
>
> *.sink.file.class=org.apache.hadoop.metrics2.sink.FileSink
> #*.sink.file.class=org.apache.hadoop.metrics2.sink.influxdb.InfluxdbSink
> #*.sink.influxdb.url=http:/xxxxxxxxxx
> #*.sink.influxdb.influxdb_port=8086
> #*.sink.influxdb.database=hadoop
> #*.sink.influxdb.influxdb_username=hadoop
> #*.sink.influxdb.influxdb_password=hadoop
> #*.sink.ingluxdb.cluster=c1
> *.period=10
> #namenode.sink.influxdb.class=org.apache.hadoop.metrics2.sink.influxdb.InfluxdbSink
> #S3AFileSystem.sink.influxdb.class=org.apache.hadoop.metrics2.sink.influxdb.InfluxdbSink
> S3AFileSystem.sink.file.filename=s3afilesystem-metrics.out
> I can't find the out put file even i run a MR job which should be used s3.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message