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-17760) Ambari should perform service check only healthy hosts
Date Sun, 17 Jul 2016 22:19:20 GMT

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

Hadoop QA commented on AMBARI-17760:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12818463/AMBARI-17760.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 1 new or modified
test files.

    {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:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

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

This message is automatically generated.

> Ambari should perform service check only healthy hosts
> ------------------------------------------------------
>
>                 Key: AMBARI-17760
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17760
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Dmytro Grinenko
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17760.patch
>
>
> We blindly pick first component in a row, if no preferred client components found
> As solution, we should check for healthy candidate, and check the case - that first selected
component could be not installed at all(i.e. not installed on any host). This could be happened
if first picked up component is a slave with cardinality 0+



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

Mime
View raw message