[
https://issues.apache.org/jira/browse/HADOOP-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Kunz updated HADOOP-1999:
-----------------------------------
Priority: Critical (was: Major)
Summary: DataNodes can become dead nodes when running 'dfsadmin
finalizeUpgrade' (was: DFSClients get stuck when running 'dfsadmin
finalizeUpgrade')
The situation was worse than initially reported. Some DataNodes became dead
nodes about at the same time, and some blocks became missing because of that. I
attached the jstack of one of the dead DataNodes.
Concerning missing blocks, It looks to me that the block id goes missing as
well (at least fsck does not report it anymore). If this is true, I would argue
that this should be fixed, because it can always happen that some DataNodes go
off-line at the same time because of bugs or network problems, and could be
brought on-line just by restarting.
> DataNodes can become dead nodes when running 'dfsadmin finalizeUpgrade'
> -----------------------------------------------------------------------
>
> Key: HADOOP-1999
> URL: https://issues.apache.org/jira/browse/HADOOP-1999
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.15.0
> Environment: Sep 14 nightly build
> Reporter: Christian Kunz
> Priority: Critical
> Attachments: jstack.datanode
>
>
> I restarted namenode with -upgrade option, started a few scripts running
> hadoop command line utility to upload a few files into dfs, and ran at some
> time
> hadoop dfsadmin -finalizeUpgrade.
> At this time all the dfs clients I started before got stuck during block
> transmission.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
