hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-4775) Nodemanager checks for old aggregated logs as the NM user instead of the app user
Date Thu, 18 Aug 2016 01:07:23 GMT

     [ https://issues.apache.org/jira/browse/YARN-4775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vinod Kumar Vavilapalli updated YARN-4775:
------------------------------------------
    Target Version/s: 2.7.4  (was: 2.7.3)

2.7.3 is under release process, changing target-version to 2.7.4.

> Nodemanager checks for old aggregated logs as the NM user instead of the app user
> ---------------------------------------------------------------------------------
>
>                 Key: YARN-4775
>                 URL: https://issues.apache.org/jira/browse/YARN-4775
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>    Affects Versions: 2.6.0
>            Reporter: Jason Lowe
>            Priority: Minor
>
> AppLogAggregatorImpl#cleanOldLogs checks for old aggregated logs as the NM user instead
of using the UGI for the app whose logs are being aggregated.  This causes an extra connection
to the namenode if the NM user wasn't already connected to the namenode.  If cleanOldLogs
does find logs to delete then it uses the UGI of the app to delete them, so it's not consistent.
 It should use the app UGI for both listing and for deleting.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message