[ http://issues.apache.org/jira/browse/HADOOP-163?page=comments#action_12376353 ]
Doug Cutting commented on HADOOP-163: ------------------------------------- But should a datanode with no disk or a read-only disk still send heartbeats to the namenode? I think not. So it should exit the datanode daemon loop. I think more than that is hard to specify at this point. You're talking about what we should do when we have a system that automatically restarts, and a system that monitors, etc. We don't have those systems in Hadoop today, so they're hard to code to! In the meantime, do you think it would be better to enter some zombie state, not sending heartbeats or otherwise participating in namenode network protocols, but looping sending out SOS over channels TBD? > If a DFS datanode cannot write onto its file system. it should tell the name > node not to assign new blocks to it. > ----------------------------------------------------------------------------------------------------------------- > > Key: HADOOP-163 > URL: http://issues.apache.org/jira/browse/HADOOP-163 > Project: Hadoop > Type: Bug > Reporter: Runping Qi > > I observed that sometime, if a file of a data node is not mounted properly, > it may not be writable. In this case, any data writes will fail. The name > node should stop assigning new blocks to that data node. The webpage should > show that node is in an abnormal state. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
