[jira] [Created] (YARN-9814) JobHistoryServer can't delete aggregated files, if remote app root directory is created by NodeManager

["Adam Antal (Jira)" <ji...@apache.org>]

Adam Antal created YARN-9814:
--------------------------------

             Summary: JobHistoryServer can't delete aggregated files, if remote app root directory is created by NodeManager
                 Key: YARN-9814
                 URL: https://issues.apache.org/jira/browse/YARN-9814
             Project: Hadoop YARN
          Issue Type: Bug
          Components: log-aggregation, yarn
    Affects Versions: 3.1.2
            Reporter: Adam Antal


If remote-app-log-dir is not created before starting Yarn processes, the NodeManager creates it during the init of AppLogAggregator service. In a custom system the primary group of the yarn user (which starts the NM/RM daemons) is not hadoop, but set to a more restricted group (say yarn). If NodeManager creates the folder it derives the group of the folder from the primary group of the login user (which is yarn:yarn in this case), thus setting the root log folder and all its subfolders to yarn group, ultimately making it unaccessible to other processes - e.g. the JobHistoryServer's AggregatedLogDeletionService.

I suggest to make this group configurable. If this new configuration is not set then we can still stick to the existing behaviour. 

Creating the root app-log-dir each time during the setup of this system is a bit error prone, and an end user can easily forget it. I think the best to put this step is the LogAggregationService, which was responsible for creating the folder already.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

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