ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sumit Mohanty (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMBARI-9973) Tarball and shared libs setup should be parallelized
Date Wed, 17 May 2017 00:43:04 GMT

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

Sumit Mohanty resolved AMBARI-9973.
-----------------------------------
    Resolution: Not A Problem

> Tarball and shared libs setup should be parallelized
> ----------------------------------------------------
>
>                 Key: AMBARI-9973
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9973
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Ivan Mitic
>            Assignee: Sumit Mohanty
>
> 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.




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

Mime
View raw message