ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan V." <iveselovs...@gridgain.com>
Subject Re: Exception in Kerberos Yarn cluster
Date Fri, 12 Feb 2016 19:41:13 GMT
Hi, Dmitriy,
but we don't seem to have a fix yet. It looks like the problem exists, but
I still was not able to see it because it is reproducible in real
multi-node kerberized cluster .

On Fri, Feb 12, 2016 at 8:26 PM, Dmitriy Setrakyan <dsetrakyan@apache.org>
wrote:

> Ivan,
>
> I think it makes sense to update the documentation with your explanation.
> Can you please do it?
>
> Thanks,
> D.
>
>
> On Fri, Feb 12, 2016 at 2:07 AM, Ivan Veselovsky <
> iveselovskiy@gridgain.com> wrote:
>
>> 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.
>>
>
>

Mime
View raw message