You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Sumit Mohanty (JIRA)" <ji...@apache.org> on 2015/09/23 07:34:04 UTC

[jira] [Resolved] (AMBARI-13196) Designate Active Ambari Server (safety lock)

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

Sumit Mohanty resolved AMBARI-13196.
------------------------------------
    Resolution: Fixed

> Designate Active Ambari Server (safety lock)
> --------------------------------------------
>
>                 Key: AMBARI-13196
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13196
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.2.0
>            Reporter: Nahappan Somasundaram
>            Assignee: Nahappan Somasundaram
>            Priority: Critical
>             Fix For: 2.2.0
>
>
> Ambari server should support a flag (in ambari.properties file) to designate itself as the active instance. The use of the flag will be limited for now but in future can be expanded. Initial use of the flag would be to:
> Log a WARN and bring down the instance - this will prevent accidental start of the Ambari Server instance
> Default status of Ambari will be active and the flag will not be present. To designate an instance to be Inactive, this flag will be used



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