[
https://issues.apache.org/jira/browse/YARN-4783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17192056#comment-17192056
]
Andras Gyori commented on YARN-4783:
------------------------------------
Thank you [~BilwaST] for attracting my attention to this case. I think it is an
absolutely probable scenario. Do you mean we should try to renew/request a
token for every HDFS token? Right now, as you say, we filter all the HDFS
tokens from the credentials, however, just get the first one from this set. Are
you suggesting to iterate over the whole set, and manage multiple token in case
of multiple nameservices?
> 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]
