Return-Path: 
 <user-return-2699-apmail-ignite-user-archive=ignite.apache.org@ignite.apache.org>
X-Original-To: apmail-ignite-user-archive@minotaur.apache.org
Delivered-To: apmail-ignite-user-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 947DB18B29
	for <apmail-ignite-user-archive@minotaur.apache.org>;
 Fri, 12 Feb 2016 10:19:28 +0000 (UTC)
Received: (qmail 8291 invoked by uid 500); 12 Feb 2016 10:19:23 -0000
Delivered-To: apmail-ignite-user-archive@ignite.apache.org
Received: (qmail 8250 invoked by uid 500); 12 Feb 2016 10:19:23 -0000
Mailing-List: contact user-help@ignite.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@ignite.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@ignite.apache.org>
List-Post: <mailto:user@ignite.apache.org>
List-Id: <user.ignite.apache.org>
Reply-To: user@ignite.apache.org
Delivered-To: mailing list user@ignite.apache.org
Received: (qmail 8240 invoked by uid 99); 12 Feb 2016 10:19:23 -0000
Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Feb 2016 10:19:23 +0000
Received: from localhost (localhost [127.0.0.1])
	by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org)
 with ESMTP id 1A7631A037C
	for <user@ignite.apache.org>; Fri, 12 Feb 2016 10:19:23 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: 0.972
X-Spam-Level: 
X-Spam-Status: No, score=0.972 tagged_above=-999 required=6.31
	tests=[RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972]
	autolearn=disabled
Received: from mx1-us-west.apache.org ([10.40.0.8])
	by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new,
 port 10024)
	with ESMTP id x9EmkEcPQKSx for <user@ignite.apache.org>;
	Fri, 12 Feb 2016 10:19:22 +0000 (UTC)
Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15])
	by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with
 ESMTP id 3628E201F7
	for <user@ignite.apache.org>; Fri, 12 Feb 2016 10:19:22 +0000 (UTC)
Received: from malf.nabble.com (unknown [162.253.133.59])
	by mbob.nabble.com (Postfix) with ESMTP id 274EE209475B
	for <user@ignite.apache.org>; Fri, 12 Feb 2016 02:13:16 -0800 (PST)
Date: Fri, 12 Feb 2016 02:07:36 -0800 (PST)
From: Ivan Veselovsky <iveselovskiy@gridgain.com>
To: user@ignite.apache.org
Message-ID: <1455271656895-2978.post@n6.nabble.com>
In-Reply-To: <1454660923545-2849.post@n6.nabble.com>
References: <1447374316660-1950.post@n6.nabble.com>
 <1447674752913-1967.post@n6.nabble.com>
 <1447709501800-1972.post@n6.nabble.com>
 <1454398913520-2801.post@n6.nabble.com> <56B077C6.50209@gridgain.com>
 <1454659518941-2847.post@n6.nabble.com>
 <1454660923545-2849.post@n6.nabble.com>
Subject: Re: Exception in Kerberos Yarn cluster
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi, harishraj,
does the initial problem persist?

I tried ignite yarn module in kerberized Hortonworks sandbox environment,
and it works (see listing below), which means that the module is able to run
Ignite nodes in containers, and all the logs are visible through Yarn web
console (http://<hostname>:8088/cluster), as the doc page
(https://apacheignite.readme.io/docs/yarn-deployment) prescribes.

An exception similar to that you initially reported can be observed if the
user does not have a valid ticket in Kerberos. So, the question is, did you
"kinit" the user before running the yarn application?





--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Exception-in-Kerberos-Yarn-cluster-tp1950p2978.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.