Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Fri, 2 Sep 2016 10:51:20 +0000 (UTC)
From: "Laszlo Puskas (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13002321.1472813404000.477984.1472813480564@Atlassian.JIRA>
In-Reply-To: <JIRA.13002321.1472813404000@Atlassian.JIRA>
References: <JIRA.13002321.1472813404000@Atlassian.JIRA> <JIRA.13002321.1472813404859@arcas>
Subject: [jira] [Updated] (AMBARI-18302) Desired state of client component
 should not be changed in case configuration changes are applied through a
 "Restart"
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 02 Sep 2016 10:51:22 -0000


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

Laszlo Puskas updated AMBARI-18302:
-----------------------------------
    Description: 
Configuration changes are propagated to host components by issuing a restart of the affected components.

In case of master components this action will start the affected components (regardless it is in INSTALLED or STARTED state) and the desired state will be set to STARTED.

In Ambari client components are always expected to be in INSTALLED state. However upon configuration changes, the desired state of these components are also set to STARTED. This may be misleading for ambari API users that determine component states by checking the desired state and actual state. (The actual state in case of client components will always be INSTALLED)

This issue addresses this problem by not updating the desired state when client components are restarted.

  was:
Configuration changes are propagated to host components by issuing a restart of the affected components.

In case of master components this action will start the affected components (regardless it is in INSTALLED or STARTED state) and the desired state will be set to STARTED.

In Ambari client components are always expected to be in INSTALLED state. However upon configuration changes, the desired state of these components are also set to STARTED. This may be misleading for ambari API users that determine component states by checking the desired state and actual state. (Tha actual state in case of client components will always be INSTALLED)

This issue addresses this problem by not updating the desired state when client components are restarted.


> Desired state of client component should not be changed in case configuration changes are applied through a "Restart"
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-18302
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18302
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Laszlo Puskas
>            Assignee: Laszlo Puskas
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Configuration changes are propagated to host components by issuing a restart of the affected components.
> In case of master components this action will start the affected components (regardless it is in INSTALLED or STARTED state) and the desired state will be set to STARTED.
> In Ambari client components are always expected to be in INSTALLED state. However upon configuration changes, the desired state of these components are also set to STARTED. This may be misleading for ambari API users that determine component states by checking the desired state and actual state. (The actual state in case of client components will always be INSTALLED)
> This issue addresses this problem by not updating the desired state when client components are restarted.


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