ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Lysnichenko (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMBARI-5282) supervisor.enable should be removed from Ambari's Storm Config section
Date Mon, 31 Mar 2014 14:49:14 GMT

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

Dmitry Lysnichenko resolved AMBARI-5282.
----------------------------------------

    Resolution: Fixed

Committed to trunk

> supervisor.enable should be removed from Ambari's Storm Config section
> ----------------------------------------------------------------------
>
>                 Key: AMBARI-5282
>                 URL: https://issues.apache.org/jira/browse/AMBARI-5282
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller, test
>    Affects Versions: 1.5.1
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>            Priority: Critical
>             Fix For: 1.5.1
>
>
> Ambari exposes the supervisor.enable property and in some early builds defaults it to
true which causes the supervisor's to not launch workers assigned to them. The supervisor's
will start up, the assignments are there, but the supervisor's just ignore them. We need to
remove the supervisor.enable from Ambari as it seems like a very dangerous switch that doesn't
have broad applicability. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message