hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benoy Antony (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-9034) "StorageTypeStats" Metric should not count failed storage.
Date Fri, 18 Dec 2015 20:34:46 GMT

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

Benoy Antony commented on HDFS-9034:
------------------------------------

Let say, node registers with  10 Storages of 2 TB. Assume none of these failed.  Assume 9
are DISK and 1 is ARCHIVE
stats.add(d) is called via updateDnStat .
StorageTypes will be recorded as DISK and ARCHIVE.

For the next hearBeat , the single ARCHIVE is reported as FAILED. 
stats.subtract(node) will be called, but it will not remove the FAILED storage.
StorageTypes will remain as DISK and ARCHIVE.

stats.add(node) will be called, but will skip the FAILED storage.
StorageTypes will remain as DISK and ARCHIVE.

Wouldn't this happen ?

> "StorageTypeStats" Metric should not count failed storage.
> ----------------------------------------------------------
>
>                 Key: HDFS-9034
>                 URL: https://issues.apache.org/jira/browse/HDFS-9034
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>            Reporter: Archana T
>            Assignee: Surendra Singh Lilhore
>         Attachments: HDFS-9034.01.patch, HDFS-9034.02.patch, HDFS-9034.03.patch, HDFS-9034.04.patch,
dfsStorage_NN_UI2.png
>
>
> When we remove one storage type from all the DNs, still NN UI shows entry of those storage
type --
> Ex:for ARCHIVE
> Steps--
> 1. ARCHIVE Storage type was added for all DNs
> 2. Stop DNs
> 3. Removed ARCHIVE Storages from all DNs
> 4. Restarted DNs
> NN UI shows below --
> DFS Storage Types
> Storage Type Configured Capacity Capacity Used Capacity Remaining 
> ARCHIVE	57.18 GB	64 KB (0%)	39.82 GB (69.64%)	64 KB	1



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

Mime
View raw message