[
https://issues.apache.org/jira/browse/YARN-4783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17177539#comment-17177539
]
Andras Gyori commented on YARN-4783:
------------------------------------
Thank you [~adam.antal] for the review. The steps of the resolution is the
following:
# The Application tries to renew the token (as we do not want to request new
token if it had not been cancelled, and also still being managed by the RM)
# If the renewal fails, then it means the token had been invalidated by the
RM, therefore we request a new one on behalf of the proxy user. We replace the
invalidated token with the new one.
# Since the new token is no longer managed by the RM, the Application makes
sure, that the token is cancelled on finishing log aggregation.
The patch has been tested on a cluster, and fixed the issue.
> Log aggregation failure for application when Nodemanager is restarted
> ----------------------------------------------------------------------
>
> Key: YARN-4783
> URL: https://issues.apache.org/jira/browse/YARN-4783
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 2.7.1
> Reporter: Surendra Singh Lilhore
> Assignee: Andras Gyori
> Priority: Major
> Attachments: YARN-4783.001.patch, YARN-4783.002.patch,
> YARN-4783.003.patch
>
>
> Scenario :
> =========
> 1.Start NM with user dsperf:hadoop
> 2.Configure linux-execute user as dsperf
> 3.Submit application with yarn user
> 4.Once few containers are allocated to NM 1
> 5.Nodemanager 1 is stopped (wait for expiry )
> 6.Start node manager after application is completed
> 7.Check the log aggregation is happening for the containers log in NMLocal
> directory
> Expect Output :
> ===============
> Log aggregation should be succesfull
> Actual Output :
> ===============
> Log aggreation not successfull
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
