[
https://issues.apache.org/jira/browse/YARN-8418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16512199#comment-16512199
]
Bibin A Chundatt commented on YARN-8418:
----------------------------------------
[~leftnoteasy]/[[email protected]]/[~jlowe]
Currently for long running services once the application failed to init at
logAggregation Server in nodemanager , log aggregation will never happen for
that application.
For long running services whose delegation token has expired this scenario is
possible after restart of nodemanager.
Submit application-> wait for token to be expired and new token generated at RM
-> restart Nodemanager.
Application init will fail at log aggregation service and log aggregation will
be disabled for application for ever even after receiving the new token from
resourcemanager.
One solution for this is enable aggregation when we receive new token from
Resource manager.
Attaching patch handling the case.
> App local logs could leaked if log aggregation fails to initialize for the app
> ------------------------------------------------------------------------------
>
> Key: YARN-8418
> URL: https://issues.apache.org/jira/browse/YARN-8418
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.8.0, 3.0.0-alpha1
> Reporter: Bibin A Chundatt
> Assignee: Bibin A Chundatt
> Priority: Critical
> Attachments: YARN-8418.001.patch, YARN-8418.002.patch
>
>
> If log aggregation fails init createApp directory container logs could get
> leaked in NM directory
> For log running application restart of NM after token renewal this case is
> possible/ Application submission with invalid delegation token
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
