hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-9279) Decomissioned capacity should not be considered for configured/used capacity
Date Wed, 28 Oct 2015 21:12:28 GMT

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

Hudson commented on HDFS-9279:
------------------------------

FAILURE: Integrated in Hadoop-Mapreduce-trunk #2539 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2539/])
HDFS-9279. Decomissioned capacity should not be considered for (kihwal: rev 19a77f546657b086af8f41fa631099bdde7e010c)
* hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestDecommission.java
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/DatanodeStats.java


> Decomissioned capacity should not be considered for configured/used capacity
> ----------------------------------------------------------------------------
>
>                 Key: HDFS-9279
>                 URL: https://issues.apache.org/jira/browse/HDFS-9279
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 2.6.1
>            Reporter: Kuhu Shukla
>            Assignee: Kuhu Shukla
>             Fix For: 3.0.0, 2.8.0
>
>         Attachments: HDFS-9279-v1.patch, HDFS-9279-v2.patch, HDFS-9279-v3.patch, HDFS-9279-v4.patch
>
>
> Capacity of a decommissioned node is being accounted as configured and used capacity
metrics. This gives incorrect perception of cluster usage.
> Once a node is decommissioned, its capacity should be considered similar to a dead node.



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

Mime
View raw message