Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 23 Sep 2013 18:19:03 +0000 (UTC)
From: "Kai Zheng (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12670097.1379953643329.4215.1379960343033@arcas>
In-Reply-To: <JIRA.12670097.1379953643329@arcas>
References: <JIRA.12670097.1379953643329@arcas>
Subject: [jira] [Commented] (HDFS-5248) Checkpointing fails in uploading the
 Image to the Namenode if the merge requires more than 10 hours in secure
 cluster
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kai Zheng commented on HDFS-5248:
---------------------------------

I guess there might be a place calling ugi.doAs or like that in the callers of putFSImage(). If so, perhaps there adding the checkTGTAndReloginFromKeytab() call might work with minimized change. HADOOP-9797 is working on something that does such job automatically. For ugi logined from keytab or ticket cache, it has choice to be automatically renewed.
                
> Checkpointing fails in uploading the Image to the Namenode if the merge requires more than 10 hours in secure cluster
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-5248
>                 URL: https://issues.apache.org/jira/browse/HDFS-5248
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 2.1.0-beta, 1.2.1
>            Reporter: Benoy Antony
>            Assignee: Benoy Antony
>         Attachments: HDFS-5248-1.patch
>
>
> If the merge takes up more than 10 hours, the TGT of the SNN expires and SNN will fail to upload the image to the Namenode

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