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

Hudson commented on AMBARI-20670:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1367 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1367/])
AMBARI-20670 Node manager start extremely slow when YARN NM local dirs (dsen: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7dcde19318d8cafc136955c019bc56ebee5fc626])
* (add) ambari-agent/src/test/python/resource_management/TestUtils.py
* (edit) ambari-common/src/main/python/resource_management/core/utils.py
* (edit) 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/yarn.py
* (edit) ambari-common/src/main/python/resource_management/core/sudo.py


> Node manager start extremely slow when YARN NM local dirs are very large
> ------------------------------------------------------------------------
>
>                 Key: AMBARI-20670
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20670
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.5.1
>            Reporter: Dmytro Grinenko
>            Assignee: Dmytro Grinenko
>            Priority: Critical
>             Fix For: trunk, 2.5.1
>
>         Attachments: AMBARI-20670-2.5.patch, AMBARI-20670.patch
>
>
> On the cluster with the YARN NM, where local dirs are 100 GB+ with lot of 
> small files - NM starts slow with timeouts
> Reason could be in this specific call in  yarn.py
> {code}
> def create_local_dir(dir_name):
>   import params
>   Directory(dir_name,
>             create_parents = True,
>             cd_access="a",
>             mode=0755,
>             owner=params.yarn_user,
>             group=params.user_group,
>             ignore_failures=True,
>             recursive_mode_flags = {'f': 'a+rw', 'd': 'a+rwx'},
>   )
> {code}
> was taking ~15 minutes per mount.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to