ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-11558) Ooozie start takes too long
Date Sat, 30 May 2015 18:12:17 GMT

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

Hudson commented on AMBARI-11558:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #2756 (See [https://builds.apache.org/job/Ambari-trunk-Commit/2756/])
AMBARI-11558. Ooozie start takes too long (aonishuk) (aonishuk: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b79fd597cd54f8029b21d247b2647695aa95a7b9)
* ambari-server/src/test/python/stacks/2.0.6/OOZIE/test_oozie_server.py
* ambari-server/src/test/python/stacks/utils/RMFTestCase.py
* ambari-common/src/main/python/resource_management/libraries/providers/hdfs_resource.py
* ambari-common/src/main/python/resource_management/core/logger.py
* ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie.py
* ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py
* ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/params_linux.py


> Ooozie start takes too long
> ---------------------------
>
>                 Key: AMBARI-11558
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11558
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.1.0
>
>
> Currently Oozie Start task takes ~3 minutes. Which includes some time-
> expensive actions like:  
> 1\. Extracting a big tar archive  
> 2\. Execute prepare-war fom it  
> 3\. Checking for hdfs directory via hadoop binary.
> 1 and 2 can be avoid on the non-first starts, by saving checksum of archive
> which was extracted, and not re-extracting it unless the checksum changed, or
> the unextracted folder is gone.
> 3 can benefit from using fast WebHDFS calls.
> **As a result for me for non-first Oozie start this reduced time of start from 180 seconds
to 13-30 seconds.**



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

Mime
View raw message