[
https://issues.apache.org/jira/browse/HDFS-14491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16904414#comment-16904414
]
Siyao Meng commented on HDFS-14491:
-----------------------------------
Also as shown in your snippet of *InvalidateBlocks#add*, this operation should
be performed for *each* datanode that has the replica. Hence the
*PendingDeletionBlocks* metric does include all replicas/EC strips.
> More Clarity on Namenode UI Around Blocks and Replicas
> ------------------------------------------------------
>
> Key: HDFS-14491
> URL: https://issues.apache.org/jira/browse/HDFS-14491
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Alan Jackoway
> Assignee: Siyao Meng
> Priority: Minor
> Attachments: HDFS-14491.001.patch
>
>
> I recently deleted more than 1/3 of the files in my HDFS installation. During
> the process of the delete, I noticed that the NameNode UI near the top has a
> line like this:
> {quote}44,031,342 files and directories, 38,988,775 blocks = 83,020,117 total
> filesystem object(s).
> {quote}
> Then lower down had a line like this:
> {quote}Number of Blocks Pending Deletion 40000000
> {quote}
> That made it appear that I was deleting more blocks than exist in the
> cluster. When that number was below the total number of blocks, I briefly
> believed I had deleted the entire cluster. In reality, the second number
> includes replicas, while the first does not.
> The UI should be clarified to indicate where "Blocks" includes replicas and
> where it doesn't. This may also have an impact on the under-replicated count.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
