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] [Updated] (HDFS-6982) nntop: top­-like tool for name node users
Date Thu, 13 Nov 2014 03:17:23 GMT

     [ https://issues.apache.org/jira/browse/HDFS-6982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Maysam Yabandeh updated HDFS-6982:
----------------------------------
    Attachment: HDFS-6982.v7.patch

[~andrew.wang], submitting the new patch revised based on your last comments.

A couple of explanations:
bq. Seems like 30min would be a more human-friendly number than 25min also
The idea was to increase the periods in exponential manner: 5^0,5^1, 5^2

bq. It also seems like an unnecessary step to also have to specify the TopAuditLogger in the
conf, if a user already specified dfs.namenode.top.periods.min. If there are periods set,
let's just also create the TopAuditLogger.
I am inclined towards redundantly specifying the audit logger in the conf. I think it would
also avoid confusion for future readers if we spell out the registered audit loggers.

> nntop: top­-like tool for name node users
> -----------------------------------------
>
>                 Key: HDFS-6982
>                 URL: https://issues.apache.org/jira/browse/HDFS-6982
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>            Reporter: Maysam Yabandeh
>            Assignee: Maysam Yabandeh
>         Attachments: HDFS-6982.patch, HDFS-6982.v2.patch, HDFS-6982.v3.patch, HDFS-6982.v4.patch,
HDFS-6982.v5.patch, HDFS-6982.v6.patch, HDFS-6982.v7.patch, nntop-design-v1.pdf
>
>
> In this jira we motivate the need for nntop, a tool that, similarly to what top does
in Linux, gives the list of top users of the HDFS name node and gives insight about which
users are sending majority of each traffic type to the name node. This information turns out
to be the most critical when the name node is under pressure and the HDFS admin needs to know
which user is hammering the name node and with what kind of requests. Here we present the
design of nntop which has been in production at Twitter in the past 10 months. nntop proved
to have low cpu overhead (< 2% in a cluster of 4K nodes), low memory footprint (less than
a few MB), and quite efficient for the write path (only two hash lookup for updating a metric).



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

Mime
View raw message