ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-15928) Ambari falsely reporting Hiveserver2 up
Date Sat, 16 Apr 2016 00:26:25 GMT


Hadoop QA commented on AMBARI-15928:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  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
                        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:
Console output:

This message is automatically generated.

> Ambari falsely reporting Hiveserver2 up
> ---------------------------------------
>                 Key: AMBARI-15928
>                 URL:
>             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
> 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

View raw message