ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sumit Mohanty (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-13463) Auto start should allow selection of components that can be auto-started
Date Sun, 18 Oct 2015 21:23:05 GMT

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

Sumit Mohanty commented on AMBARI-13463:
----------------------------------------

This change replies on ambari.properties file specifying the need for auto restart. The plan
is to move to cluster-env where the users can dynamically specify configuration for recovery
without having to restart the server.

> Auto start should allow selection of components that can be auto-started
> ------------------------------------------------------------------------
>
>                 Key: AMBARI-13463
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13463
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.3
>            Reporter: Sumit Mohanty
>            Assignee: Sumit Mohanty
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-13463.patch
>
>
> Currently, auto start feature is a all-on or all-off. At times it is necessary to allow
auto-start for certain components or disallow auto-start for certain components.
> Scenarios being:
> * Do not auto-restart NAMENODE
> * Restart only AMS Collector or Storm Supervisor
> * Do not auto restart ATS/JHS as they are externally managed for HA (active-passive)



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

Mime
View raw message