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-14973) [s3a] Log StorageStatistics
Date Fri, 27 Oct 2017 21:24:00 GMT

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

Sean Mackrory commented on HADOOP-14973:

{quote}discouraging any attempts to avoid metrics2{quote}

No I'm absolutely going to look into metrics2 and strongly consider it as the right solution
for what I'm trying to do. On that note, in HADOOP-14972, you suggested I look at HADOOP-14475.
I'm taking a look at it now and it seems to actually be extremely relevant to this discussion
- I suspect you actually meant to link that here instead?

> [s3a] Log StorageStatistics
> ---------------------------
>                 Key: HADOOP-14973
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14973
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 3.0.0-beta1, 2.8.1
>            Reporter: Sean Mackrory
>            Assignee: Sean Mackrory
> S3A is currently storing much more detailed metrics via StorageStatistics than are logged
in a MapReduce job. Eventually, it would be nice to get Spark, MapReduce and other workloads
to retrieve and store these metrics, but it may be some time before they all do that. I'd
like to consider having S3A publish the metrics itself in some form. This is tricky, as S3A
has no daemon but lives inside various other processes.
> Perhaps writing to a log file at some configurable interval and on close() would be the
best we could do. Other ideas would be welcome.

This message was sent by Atlassian JIRA

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

View raw message