hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-289) Datanodes need to catch SocketTimeoutException and UnregisteredDatanodeException
Date Thu, 08 Jun 2006 02:43:30 GMT
     [ http://issues.apache.org/jira/browse/HADOOP-289?page=all ]

Konstantin Shvachko updated HADOOP-289:
---------------------------------------

    Attachment: DatanodeExceptions.patch

This patch fixes the two problems described.
I placed all registration logic inside the DataNode.register(), seems more logical to me.
There is also a simple null value checkup included for FSNamesystem,
didn't want to create a separate  issue for that.


> 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.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


Mime
View raw message