ambari-dev mailing list archives

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

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

Andrew Onischuk resolved AMBARI-11558.
--------------------------------------
    Resolution: Fixed

Committed to trunk

> 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