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-16215) Ambari starts the right component when multi instances are deployed (e.g. AMS)
Date Thu, 08 Sep 2016 16:02:21 GMT

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

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

> Ambari starts the right component when multi instances are deployed (e.g. AMS)
> ------------------------------------------------------------------------------
>
>                 Key: AMBARI-16215
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16215
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>            Reporter: Sebastian Toader
>             Fix For: 2.4.2
>
>
> Currently, components that are HA through externally managed failover are deployed with
the desired state INSTALLED - AMS Collector and JHS/ATS. Ambari can auto-start them on a specific
host during the deployment if it is possible to guarantee that for the duration of initial
cluster deployment the host  is always available.



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

Mime
View raw message