From yarn-issues-return-137727-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Mon Feb 12 10:18:04 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 352AD180652 for ; Mon, 12 Feb 2018 10:18:04 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 24D25160C61; Mon, 12 Feb 2018 09:18:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 66F14160C31 for ; Mon, 12 Feb 2018 10:18:03 +0100 (CET) Received: (qmail 77813 invoked by uid 500); 12 Feb 2018 09:18:02 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 77797 invoked by uid 99); 12 Feb 2018 09:18:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Feb 2018 09:18:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id EE0DAC004A for ; Mon, 12 Feb 2018 09:18:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.311 X-Spam-Level: X-Spam-Status: No, score=-110.311 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id uLF33TUdfC2D for ; Mon, 12 Feb 2018 09:18:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id D8AC65F2EC for ; Mon, 12 Feb 2018 09:18:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 68FC9E01BE for ; Mon, 12 Feb 2018 09:18:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 28657240F6 for ; Mon, 12 Feb 2018 09:18:00 +0000 (UTC) Date: Mon, 12 Feb 2018 09:18:00 +0000 (UTC) From: =?utf-8?Q?Berry_=C3=96sterlund_=28JIRA=29?= To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (YARN-7922) Yarn dont resolve rm/_HOST to hostname MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Berry =C3=96sterlund created YARN-7922: ------------------------------------- Summary: Yarn dont resolve rm/_HOST to hostname Key: YARN-7922 URL: https://issues.apache.org/jira/browse/YARN-7922 Project: Hadoop YARN Issue Type: Bug Components: yarn Affects Versions: 2.7.3 Reporter: Berry =C3=96sterlund The normal auth_to_local usually removes everything after the / in the user= name of the Kerberos principle. That, together with the _HOST setting in th= e configuration files specifying the Kerberos principles is usually what is= required to convert rm/_HOST@ to user yarn. In our environment, we cant use the default rules in auth_to_local. We have= to specify each and every host and only convert those specifically. In oth= er words, we don=E2=80=99t have the DEFAULT rule in auth_to_local. Ideally,= the config for us would be the following {code:java} RULE:[1:$1@$0](rm@)s/.*/invalid_user/ RULE:[2:$1/$2@$0](rm/rm1_host.fulldomain@)s/.*/yarn/ RULE:[2:$1/$2@$0](rm/rm2_host.fulldomain@)s/.*/yarn/ {code} But if we use only that configuration, the servicecheck in Ambari failes wi= th the following exception. {code:java} org.apache.hadoop.yarn.exceptions.YarnException: Failed to submit applicati= on_1518422080198_0002 to YARN : Failed to renew token: Kind: HDFS_DELEGATIO= N_TOKEN, Service: ha-hdfs:devhadoop, Ident: (HDFS_DELEGATION_TOKEN token 11= 096 for ambari-qa) at org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.submitApplication(= YarnClientImpl.java:272) at org.apache.hadoop.yarn.applications.distributedshell.Client.run(Client.j= ava:708) at org.apache.hadoop.yarn.applications.distributedshell.Client.main(Client.= java:215) {code} =C2=A0 Inside the RM=E2=80=99s logfile, I can find the following. {code:java} Caused by: org.apache.hadoop.security.AccessControlException: yarn tries to= renew a token with renewer rm/_HOST@ {code} Adding the following rule to auth_to_local solves the problem RULE:[2:$1/$2@$0](rm/_HOST@)s/.*/yarn/ The client used to test this is executed with the following command yarn org.apache.hadoop.yarn.applications.distributedshell.Client -shell_co= mmand ls -num_containers 1 -jar /usr/hdp/current/hadoop-yarn-client/hadoop-= yarn-applications-distributedshell.jar -timeout 300000 --queue -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org