ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-13196) Designate Active Ambari Server (safety lock)
Date Wed, 23 Sep 2015 08:48:04 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-13196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14904183#comment-14904183
] 

Hudson commented on AMBARI-13196:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #3492 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3492/])
AMBARI-13196. Designate Active Ambari Server (Nahappan Somasundaram via smohanty) (smohanty:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e24e3c8b75ad7b466d7ab82ebb4ffb6ac6ee6dcc)
* ambari-server/src/main/python/ambari_server/serverConfiguration.py
* ambari-server/src/main/python/ambari_server_main.py
* ambari-server/src/test/python/TestAmbariServer.py


> 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)

Mime
View raw message