[
https://issues.apache.org/jira/browse/AMBARI-4320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13903491#comment-13903491
]
Dmitry Lysnichenko commented on AMBARI-4320:
--------------------------------------------
[~mahadev]/[~sumitmohanty], I've talked to [~dsen] regarding his work on
RESTART command (ticket name is "Actual configs not updated after restart of
host component"). Looks like he is working on the opposite conception.
Implementation proposal that has been agreed in current jira specifies that we
remove explicit configure() calls from the python code and generate CONFIGURE
command for every START command being issued.
Proposal posted at Dmytro's jira specifies that RESTART command calls start()
method and invokes before-START hooks. Either start() method or hooks contain
implicit configure() call and that is how configuration is performed.
Need some unified requirements here. Probably it makes sense to leave explicit
configure() calls as is and never have to issue a separate CONFIGURE command
(go the Dmytro's way). Or agent may compare saved and current config-tags on
every START/RESTART command and perform reconfiguration if needed.
> 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)
