[ http://issues.apache.org/jira/browse/HADOOP-289?page=comments#action_12415467 ]
Owen O'Malley commented on HADOOP-289: -------------------------------------- Please replace the getLocalizedMessage and implicit toString with calls to StringUtils.stringifyException, which includes both the message and the call stack. The call stack helps a lot in finding and debugging the problem. > Datanodes need to catch SocketTimeoutException and > UnregisteredDatanodeException > -------------------------------------------------------------------------------- > > Key: HADOOP-289 > URL: http://issues.apache.org/jira/browse/HADOOP-289 > Project: Hadoop > Type: Bug > Components: dfs > Versions: 0.3.1 > Reporter: Konstantin Shvachko > Assignee: Konstantin Shvachko > Fix For: 0.3.2 > Attachments: DatanodeExceptions-2.patch, DatanodeExceptions.patch > > - Datanode needs to catch SocketTimeoutException when registering otherwise > it goes down > the same way as when the namenode is not available (HADOOP-282). > - UnregisteredDatanodeException need to be caught for all non-registering > requests. The data > node should be shutdown in this case. Otherwise it will loop infinitely and > consume namenode resources. -- 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
