You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Bilwa S T (Jira)" <ji...@apache.org> on 2020/08/17 17:46:00 UTC

[jira] [Comment Edited] (YARN-4783) Log aggregation failure for application when Nodemanager is restarted

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

Bilwa S T edited comment on YARN-4783 at 8/17/20, 5:45 PM:
-----------------------------------------------------------

Thanks [~gandras] for patch.

This may not work in multiple nameservice setup in case if you are requesting for a new token. currently client handles getting delegation token from all nameservices . whereas in your patch i see that you are just trying to get current nameservice token correct me if i am wrong.

I am talking about a case where yarn.nodemanager.remote-app-log-dir is set to a namespace that is not default-fs


was (Author: bilwast):
Thanks [~gandras] for patch.

This may not work in multiple nameservice setup in case if you are requesting for a new token. currently client handles getting delegation token from all nameservices . whereas in your patch i see that you are just trying to get current nameservice token correct me if i am wrong.

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