[ 
https://issues.apache.org/jira/browse/HDFS-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448754#comment-13448754
 ] 

Hudson commented on HDFS-1490:
------------------------------

Integrated in Hadoop-Mapreduce-trunk #1187 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1187/])
    HDFS-1490. TransferFSImage should timeout. Contributed by Dmytro Molkov and 
Vinay. (Revision 1380988)

     Result = SUCCESS
todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1380988
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSConfigKeys.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/TransferFsImage.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestTransferFsImage.java

                
> TransferFSImage should timeout
> ------------------------------
>
>                 Key: HDFS-1490
>                 URL: https://issues.apache.org/jira/browse/HDFS-1490
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>            Reporter: Dmytro Molkov
>            Assignee: Vinay
>            Priority: Minor
>             Fix For: 3.0.0, 2.2.0-alpha
>
>         Attachments: HDFS-1490.patch, HDFS-1490.patch, HDFS-1490.patch, 
> HDFS-1490.patch
>
>
> Sometimes when primary crashes during image transfer secondary namenode would 
> hang trying to read the image from HTTP connection forever.
> It would be great to set timeouts on the connection so if something like that 
> happens there is no need to restart the secondary itself.
> In our case restarting components is handled by the set of scripts and since 
> the Secondary as the process is running it would just stay hung until we get 
> an alarm saying the checkpointing doesn't happen.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to