Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Wed, 5 Sep 2012 17:27:08 +1100 (NCT)
From: "Vinay (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <1145366792.37646.1346826428421.JavaMail.jiratomcat@arcas>
In-Reply-To: <4007362.39761288982082841.JavaMail.jira@thor>
Subject: [jira] [Assigned] (HDFS-1490) TransferFSImage should timeout
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinay reassigned HDFS-1490:
---------------------------

    Assignee: Vinay  (was: Dmytro Molkov)
    
> 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