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 2014/01/17 18:40:19 UTC
[jira] [Comment Edited] (AMBARI-4320) Add separate CONFIGURE
command support to server
[ https://issues.apache.org/jira/browse/AMBARI-4320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13874987#comment-13874987 ]
Sumit Mohanty edited comment on AMBARI-4320 at 1/17/14 5:38 PM:
----------------------------------------------------------------
[~dmitriusan], how about wiring up START command to always do a configure and then start. This will also fix the RESTART issue where RESTART was not applying new configuration.
That way we have CONFIGURE as a command available for scenarios that do not require START - e.g. client components.
[~mahadev], what's your recommendation?
was (Author: sumitmohanty):
[~dmitriusan], how about wiring up START command to always do a configure and then start. This will also fix the RESTART issue where RESTART was not applying new configuration.
That way we have CONFIGURE as a command available for scenarios that do not require START - e.g. client components.
> Add separate CONFIGURE command support to server
> ------------------------------------------------
>
> Key: AMBARI-4320
> URL: https://issues.apache.org/jira/browse/AMBARI-4320
> Project: Ambari
> Issue Type: Improvement
> Components: controller
> Affects Versions: 1.5.0
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 1.5.0
>
>
> CONFIGURE command is responsible for creating files/dirs, adjusting ownership, generating config files etc.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)