[
https://issues.apache.org/jira/browse/YARN-4783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17192717#comment-17192717
]
Andras Gyori commented on YARN-4783:
------------------------------------
Thanks [~BilwaST] for the feedback. I agree with the conception you describe,
however, checking remote-app-log-dir for the namespace seems error prone to me.
As I have anticipated, the nameservice, under which the token is stored, is an
IP address, but as I see it, the namespace is often a fully qualified hostname.
The credential stores all the tokens, thus handling every HDFS token would
solve this problem as well. As far as I know, the DelegationTokenRenewer,
which is used by the ResourceManager is also using a similar technique. What is
your opinion?
> 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]
