ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-18302) Desired state of client component should not be changed in case configuration changes are applied through a "Restart"
Date Fri, 02 Sep 2016 17:28:21 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-18302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15459105#comment-15459105
] 

Hadoop QA commented on AMBARI-18302:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12826812/AMBARI-18302.trunk.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:red}-1 core tests{color}.  The test build failed in ambari-server 

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/8566//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/8566//console

This message is automatically generated.

> 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
>             Fix For: trunk
>
>         Attachments: AMBARI-18302.trunk.patch
>
>   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)

Mime
View raw message