hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maysam Yabandeh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7426) Change nntop JMX format to be a JSON blob
Date Wed, 10 Dec 2014 06:44:12 GMT

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

Maysam Yabandeh commented on HDFS-7426:
---------------------------------------

bq. Can we put the catch inside the for loop, so that one failure doesn't terminate the loop?
The idea behind the following code was to avoid any *unexpected* bug in the nntop to affect
the normal operaiton of the NN.
{code}
    } catch (Throwable t) {
{code}
So the higher its position the better. In fact I am thinking we can move it up to the TopAuditLogger
around this line
{code}
    topMetrics.report(succeeded, userName, addr, cmd, src, dst, status);
{code}

> Change nntop JMX format to be a JSON blob
> -----------------------------------------
>
>                 Key: HDFS-7426
>                 URL: https://issues.apache.org/jira/browse/HDFS-7426
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>    Affects Versions: 2.7.0
>            Reporter: Andrew Wang
>            Assignee: Andrew Wang
>         Attachments: hdfs-7426.001.patch, hdfs-7426.002.patch
>
>
> After discussion with [~maysamyabandeh], we think we can adjust the JMX output to instead
be a richer JSON blob. This should be easier to parse and also be more informative.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message