[
https://issues.apache.org/jira/browse/HDFS-6982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14211778#comment-14211778
]
Maysam Yabandeh commented on HDFS-6982:
---------------------------------------
The findbugs warning seems unrelated:
{code}
In class org.apache.hadoop.hdfs.DFSOutputStream$Packet
Field org.apache.hadoop.hdfs.DFSOutputStream$Packet.dataPos
Synchronized 83% of the time
Unsynchronized access at DFSOutputStream.java:[line 348]
Synchronized access at DFSOutputStream.java:[line 268]
Synchronized access at DFSOutputStream.java:[line 271]
Synchronized access at DFSOutputStream.java:[line 272]
Synchronized access at DFSOutputStream.java:[line 272]
Synchronized access at DFSOutputStream.java:[line 261]
Synchronized access at DFSOutputStream.java:[line 294]
{code}
Also I have difficutlies relating the failed test to audit logging:
{code}
org.apache.hadoop.hdfs.TestLeaseRecovery2.org.apache.hadoop.hdfs.TestLeaseRecovery2
{code}
> 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, HDFS-6982.v8.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)
