hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-1348) Improve NameNode reponsiveness while it is checking if datanode decommissions are complete
Date Fri, 06 Feb 2015 23:11:36 GMT

     [ https://issues.apache.org/jira/browse/HDFS-1348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Allen Wittenauer updated HDFS-1348:
-----------------------------------
    Status: Patch Available  (was: Open)

> Improve NameNode reponsiveness while it is checking if datanode decommissions are complete
> ------------------------------------------------------------------------------------------
>
>                 Key: HDFS-1348
>                 URL: https://issues.apache.org/jira/browse/HDFS-1348
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>            Reporter: Hairong Kuang
>            Assignee: Hairong Kuang
>         Attachments: decomissionImp1.patch, decomissionImp2.patch, decommission.patch,
decommission1.patch
>
>
> NameNode normally is busy all the time. Its log is full of activities every second. But
once for a while, NameNode seems to pause for more than 10 seconds without doing anything,
leaving a blank in its log even though no garbage collection is happening.  All other requests
to NameNode are blocked when this is happening.
> One culprit is DecommionManager. Its monitor holds the fsynamesystem lock during the
whole process of checking if decomissioning DataNodes are finished or not, during which it
checks every block of up to a default of 5 datanodes.



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

Mime
View raw message