[
https://issues.apache.org/jira/browse/IGNITE-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144627#comment-15144627
]
Luca Rea commented on IGNITE-2525:
----------------------------------
Hi Ivan,
all others yarn applications (hdfs client, hive, hbase, spark, both mapreduce
and tez, knox, etc.) work correctly, the problem is not strictly related to log
time running application nor to log aggregation itself, the ignite module
starts the yarn containers (in the job manager you can see it tagged as
RUNNING) but those encounter the token exception and exit (the final tag is
FAILED), so it's not possible to keep an ignite cluster up and running and
maybe it doesn't complete the starting process at all.
> Yarn - Kerberos delegation token support for long running applications
> ----------------------------------------------------------------------
>
> Key: IGNITE-2525
> URL: https://issues.apache.org/jira/browse/IGNITE-2525
> Project: Ignite
> Issue Type: Improvement
> Affects Versions: 1.5.0.final
> Reporter: Luca Rea
> Assignee: Ivan Veselovsky
> Fix For: 1.6
>
>
> Hi,
> now Yarn returns an authentication error when kerberos is enabled:
> java.io.IOException: Failed on local exception: java.io.IOException:
> org.apache.hadoop.security.AccessControlException: Client cannot authenticate
> via:[TOKEN, KERBEROS];
> I think Apache Ignite needs somethink like "AMDelegationTokenRenewer.scala"
> and "ExecutorDelegationTokenUpdater.scala" of Apache Spark to support long
> running applications in clusters with kerberos authantication enabled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
