You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Antonenko Alexander (JIRA)" <ji...@apache.org> on 2016/04/15 18:38:25 UTC
[jira] [Commented] (AMBARI-2330) Ambari should support "auto start"
and "desired state" of service components
[ https://issues.apache.org/jira/browse/AMBARI-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15243187#comment-15243187 ]
Antonenko Alexander commented on AMBARI-2330:
---------------------------------------------
This was resolved in branch of tickets. Like AMBARI-14983, AMBARI-15194, AMBARI-15592 and other
> Ambari should support "auto start" and "desired state" of service components
> ----------------------------------------------------------------------------
>
> Key: AMBARI-2330
> URL: https://issues.apache.org/jira/browse/AMBARI-2330
> Project: Ambari
> Issue Type: Improvement
> Affects Versions: 1.2.4
> Reporter: Jeff Sposetti
> Fix For: 2.4.0
>
>
> Ambari Server and Agents can be setup to auto-start on system reboot (using the init.d scripts)
> In the case of hadoop Components (like NN, JT, DN, etc), the user has to go into Ambari and click "start", which can be cumbersome. And if missed/forgotten, can cause unintended outages.
> Ambari should impose "desired" service state, with the ability to designate "auto start".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)