ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jayush Luniya (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-16213) Initial Start All should be similar to a later Start All
Date Thu, 08 Sep 2016 16:01:20 GMT

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

Jayush Luniya updated AMBARI-16213:
-----------------------------------
    Fix Version/s:     (was: 2.4.1)
                   2.4.2

> Initial Start All should be similar to a later Start All
> --------------------------------------------------------
>
>                 Key: AMBARI-16213
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16213
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>            Reporter: Sebastian Toader
>             Fix For: 2.4.2
>
>
> Starting a cluster in a pre-provisioned environment should need minimal setup activities.
So first start should not be different than any start from a full-stop. Of course, it is not.
Typical differences are:
> * Files and folders do not exist and are created (config files, log folders, etc.)
> * Several services perform initialization - AMS/HDFS/OOZIE
> Investigate what operations from the initial Start-All that can be moved to sys-provisioning
step and what can be optimized in general.



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

Mime
View raw message