[AMBARI-9973] Tarball and shared libs setup should be parallelized

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Not A Problem
• Assignee: Sumit Mohanty
• Reporter: Ivan Mitic
• Created: 07/Mar/15 00:42
• Updated: 17/May/17 00:42
• Resolved: 17/May/17 00:42

Description

We noticed that in latest Ambari and HDP 2.2, significant amount of cluster deployment time goes into tarball and shared lib upload to the default file system.
For example, Oozie component START command takes 8-10 minutes in total.

This is a tracking Jira to parallelize some of these tasks to a separate thread in the stack definition, as this is expected to significantly decrease the overall deployment latency.

Issue Links

• is part of: AMBARI-8188 Improve Ambari deployment performance in cloud environments