Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Tue, 19 Apr 2016 15:26:25 +0000 (UTC)
From: "Junping Du (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12941395.1456234009000.267950.1461079585577@Atlassian.JIRA>
In-Reply-To: <JIRA.12941395.1456234009000@Atlassian.JIRA>
References: <JIRA.12941395.1456234009000@Atlassian.JIRA>
 <JIRA.12941395.1456234009981@arcas>
Subject: [jira] [Commented] (YARN-4721) RM to try to auth with HDFS on
 startup, retry with max diagnostics on failure
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Junping Du commented on YARN-4721:
----------------------------------

bq. I'm going to propose "hadoop.security.kerberos.diagnostics", rather than an RM specific one. That way, the code can be replicated in the NMs and the HDFS components, with the same outcome: hadoop diagnostics
+1. That sounds reasonable. Shall we split the JIRA into two - one for Hadoop project code and one for YARN?

> RM to try to auth with HDFS on startup, retry with max diagnostics on failure
> -----------------------------------------------------------------------------
>
>                 Key: YARN-4721
>                 URL: https://issues.apache.org/jira/browse/YARN-4721
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: resourcemanager
>    Affects Versions: 2.8.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>         Attachments: HADOOP-12889-001.patch
>
>
> If the RM can't auth with HDFS, this can first surface during job submission, which can cause confusion about what's wrong and whose credentials are playing up.
> Instead, the RM could try to talk to HDFS on launch, {{ls /}} should suffice. If it can't auth, it can then tell UGI to log more and retry.
> I don't know what the policy should be if the RM can't auth to HDFS at this point. Certainly it can't currently accept work. But should it fail fast or keep going in the hope that the problem is in the KDC or NN and will fix itself without an RM restart?


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)