[
https://issues.apache.org/jira/browse/IGNITE-8812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nithyananthan N P closed IGNITE-8812.
-------------------------------------
> Ignite Yarn HDFS delegation token expiry issue
> ----------------------------------------------
>
> Key: IGNITE-8812
> URL: https://issues.apache.org/jira/browse/IGNITE-8812
> Project: Ignite
> Issue Type: Bug
> Components: yarn
> Affects Versions: 2.3
> Environment: Version : 2.3.0
> Module : Ignite-YARN
> Class : ApplicationMaster
> Platform : Cloudera 2.6.0-cdh5.11.2
> Reporter: Nithyananthan N P
> Priority: Major
>
> Hello,
> As Ignite-YARN is a long running application in YARN environment it should
> have a mechanism to renew the delegation token.
>
> In Ignite-YARN, when the ApplicationMaster is started, it acquires Delegation
> tokens and stores in a ByteBuffer[Class: ApplicationMaster, Method: init()].
> This ByteBuffer with token information is given to all the containers
> received from ResourceManager [Class: ApplicationMaster, Method:
> onContainersAllocated()].
> Everything works fine till the life time of the delegation token.
> Once the delegation token expires, the ApplicationMaster is not able to start
> Ignite inside containers it receive and below exception occurs
>
>
>
> ApplicationMaster keeps on asking for more and more containers [Class:
> ApplicationMaster, Method: run()] but not able to start Ignite inside any of
> the containers due to the expired/missing delegation token.
> This repeats until all the resources in the cluster are allocated to Ignition.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)