[ 
https://issues.apache.org/jira/browse/YARN-8418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562026#comment-16562026
 ] 

Wangda Tan commented on YARN-8418:
----------------------------------

[~rohithsharma], regarding to the YARN-4984 revert, Initially I have doubt as 
well, now I'm convinced. See my comment at: 
https://issues.apache.org/jira/browse/YARN-8418?focusedCommentId=16551034&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16551034

Regarding to delegation token change, let's wait [~bibinchundatt]'s response. 

> 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: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to