[jira] Created: (HDFS-1125) Removing a datanode (failed or decommissioned) should not require a namenode restart
Removing a datanode (failed or decommissioned) should not require a namenode restart Key: HDFS-1125 URL: https://issues.apache.org/jira/browse/HDFS-1125 Project: Hadoop HDFS Issue Type: Bug Components: name-node Reporter: Alex Loddengaard Priority: Minor I've heard of several Hadoop users using dfsadmin -report to monitor the number of dead nodes, and alert if that number is not 0. This mechanism tends to work pretty well, except when a node is decommissioned or fails, because then the namenode requires a restart for said node to be entirely removed from HDFS. More details here: http://markmail.org/search/?q=decommissioned%20node%20showing%20up%20ad%20dead%20node%20in%20web%20based%09interface%20to%20namenode#query:decommissioned%20node%20showing%20up%20ad%20dead%20node%20in%20web%20based%09interface%20to%20namenode+page:1+mid:7gwqwdkobgfuszb4+state:results Removal from the exclude file and a refresh should get rid of the dead node. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (HDFS-1126) Change HDFS to depend on Hadoop 'common' artifacts instead of 'core'
Change HDFS to depend on Hadoop 'common' artifacts instead of 'core' Key: HDFS-1126 URL: https://issues.apache.org/jira/browse/HDFS-1126 Project: Hadoop HDFS Issue Type: Improvement Reporter: Tom White Priority: Blocker Fix For: 0.21.0 This is the HDFS part of HADOOP-6404. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (HDFS-1127) Improve the speed of FileSystem object creation
Improve the speed of FileSystem object creation
---
Key: HDFS-1127
URL: https://issues.apache.org/jira/browse/HDFS-1127
Project: Hadoop HDFS
Issue Type: Improvement
Affects Versions: 0.20.2, 0.20.1
Reporter: Zheng Shao
Assignee: Zheng Shao
It takes a long time to create a lot of {{DistributedFileSystem}} object via
{{FileSystem.create}} or {{FileSystem.createNewInstance}} function.
In our experience with scribe-hdfs, it can take up to 2 minutes for 100 such
calls from each node of a cluster of 40 nodes.
The reason for the delay is mainly because of the lock on the CACHE object. We
should release the lock while creating new FileSystem objects.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
