[jira] [Commented] (AMBARI-20851) Provide Alert For Component OUT_OF_SYNC Issues

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-20851:
------------------------------------

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

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

    {color:green}+1 tests included{color}.  The patch appears to include 3 new or modified test files.

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

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

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11490//console

This message is automatically generated.

> Provide Alert For Component OUT_OF_SYNC Issues
> ----------------------------------------------
>
>                 Key: AMBARI-20851
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20851
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.5.1
>
>         Attachments: AMBARI-20851.patch
>
>
> Components can become {{OUT_OF_SYNC}} before and after stack upgrades. As a result, this can affect the success of future upgrade attempts. It seems wrong to expose a direct way to alter this state since it's calculated from the agents.
> - The logic currently for reporting component versions is as follows:
> -- On an agent's initial heartbeat registration, status commands will report component versions. Subsequent status commands will not.
> -- On any START/STOP/RESTART, the component will report a version
> This means that if a host is {{OUT_OF_SYNC}} there are two ways to automatically fix it (assuming the cluster is properly upgraded)
> - Restart the agent on that host
> - Restart the components which are {{OUT_OF_SYNC}} on that host
> It would be good to notify the cluster administrator that there is a problem with the reported version of the components.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)