[
https://issues.apache.org/jira/browse/YARN-8418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16561804#comment-16561804
]
Rohith Sharma K S commented on YARN-8418:
-----------------------------------------
Thanks [~bibinchundatt] for the patch! Approach of updating token looks
reasonable to me. But I have basic doubt on scenario you are mentioning
Why does token changed? It should be same during lifespan of application right?
IIUC, token will be renewed but not going to be changed right?
IIUC the problem, YARN-4984 try to fixes for stale applications i.e which are
completed from RM. In this case, token could be cancelled before NM removes
from its statestore which could lead problem mentioned as YARN-4984.
In attached patch, YARN-4984 fix is reverted and method
checkAndEnableAppAggregators ignores the exception. So thread leak persist
after this patch.
> 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,
> YARN-8418.003.patch, YARN-8418.004.patch, YARN-8418.005.patch,
> YARN-8418.006.patch, YARN-8418.007.patch, YARN-8418.008.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]
