[jira] [Commented] (AMBARI-15928) Ambari falsely reporting Hiveserver2 up

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

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

Hadoop QA commented on AMBARI-15928:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12798993/AMBARI-15928.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:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

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

This message is automatically generated.

> Ambari falsely reporting Hiveserver2 up
> ---------------------------------------
>
>                 Key: AMBARI-15928
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15928
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-15928.patch
>
>
> PROBLEM:
> After adding a custom whitelist.append value (incorrect value), and using Ambari server to complete a 'clean' stop/start of all Hive components, it fails to bring up Hiveserver2 properly (but reports successful ambari-agent task).
> Update:
> After 30 attempts (30mins of looping) to start Hiveserver2, the log finally ended at this point



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