[
https://issues.apache.org/jira/browse/HDFS-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kihwal Lee updated HDFS-4832:
-----------------------------
Resolution: Fixed
Fix Version/s: 0.23.9
2.1.0-beta
3.0.0
Release Note: This change makes name node keep its internal replication
queues and data node state updated in manual safe mode. This allows metrics and
UI to present up-to-date information while in safe mode. The behavior during
start-up safe mode is unchanged.
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
I've committed this to trunk, branch-2, branch-2.1.0-beta, and branch-0.23.
Thanks for working on this patch, Ravi.
> Namenode doesn't change the number of missing blocks in safemode when DNs
> rejoin or leave
> -----------------------------------------------------------------------------------------
>
> Key: HDFS-4832
> URL: https://issues.apache.org/jira/browse/HDFS-4832
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 3.0.0, 0.23.7, 2.1.0-beta
> Reporter: Ravi Prakash
> Assignee: Ravi Prakash
> Priority: Critical
> Fix For: 3.0.0, 2.1.0-beta, 0.23.9
>
> Attachments: HDFS-4832.branch-0.23.patch, HDFS-4832.patch,
> HDFS-4832.patch, HDFS-4832.patch, HDFS-4832.patch, HDFS-4832.patch,
> HDFS-4832.patch
>
>
> Courtesy Karri VRK Reddy!
> {quote}
> 1. Namenode lost datanodes causing missing blocks
> 2. Namenode was put in safe mode
> 3. Datanode restarted on dead nodes
> 4. Waited for lots of time for the NN UI to reflect the recovered blocks.
> 5. Forced NN out of safe mode and suddenly, no more missing blocks anymore.
> {quote}
> I was able to replicate this on 0.23 and trunk. I set
> dfs.namenode.heartbeat.recheck-interval to 1 and killed the DN to simulate
> "lost" datanode. The opposite case also has problems (i.e. Datanode failing
> when NN is in safemode, doesn't lead to a missing blocks message)
> Without the NN updating this list of missing blocks, the grid admins will not
> know when to take the cluster out of safemode.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
