[AMBARI-11558] Ooozie start takes too long

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.1.0
• Epic Link: Ambari is too slow to start/restart
• Assignee: Andrew Onischuk
• Reporter: Andrew Onischuk
• Created: 30/May/15 16:20
• Updated: 11/Oct/16 10:55
• Resolved: 30/May/15 16:24

Description

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.*

Issue Links

• breaks: AMBARI-18567 Cannot start Oozie if WebHDFS is disabled
• links to: ReviewBoard