[
https://issues.apache.org/jira/browse/HDFS-10987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15572902#comment-15572902
]
Hudson commented on HDFS-10987:
-------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #10606 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/10606/])
HDFS-10987. Make Decommission less expensive when lot of blocks present.
(kihwal: rev 332a61fd74fd2a9874319232c583ab5d2c53ff03)
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/DecommissionManager.java
> Make Decommission less expensive when lot of blocks present.
> ------------------------------------------------------------
>
> Key: HDFS-10987
> URL: https://issues.apache.org/jira/browse/HDFS-10987
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Brahma Reddy Battula
> Assignee: Brahma Reddy Battula
> Priority: Critical
> Attachments: HDFS-10987-002.patch, HDFS-10987.patch
>
>
> When user want to decommission a node which having 50M blocks +,it could hold
> the namesystem lock for long time.We've seen it is taking 36 sec+.
> As we knew during this time, Namenode will not available... As this
> decommission will continuosly run till all the blocks got replicated,hence
> Namenode will unavailable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
