You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Konstantin Shvachko (JIRA)" <ji...@apache.org> on 2017/05/08 23:54:04 UTC
[jira] [Updated] (HDFS-10987) Make Decommission less expensive when
lot of blocks present.
[ https://issues.apache.org/jira/browse/HDFS-10987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Shvachko updated HDFS-10987:
---------------------------------------
Labels: release-blocker (was: )
Target Version/s: 2.7.4
> 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
> Labels: release-blocker
> Fix For: 2.8.0, 3.0.0-alpha2
>
> 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.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org