[
https://issues.apache.org/jira/browse/AMBARI-9655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14322265#comment-14322265
]
Hadoop QA commented on AMBARI-9655:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12699013/AMBARI-9655.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 .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/1702//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1702//console
This message is automatically generated.
> Added Second Hive Metastore, two alert instances but both OK
> ------------------------------------------------------------
>
> Key: AMBARI-9655
> URL: https://issues.apache.org/jira/browse/AMBARI-9655
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.0.0
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-9655.patch
>
>
> 1) Added second Hive Metastore.
> 2) Once it's done installing, all properties are set and the component is
> installed (but stopped) - correct.
> 3) The Hive Metastore process alert now has two instances - correct
> 4) But both alert instances are OK (even for the new Hive Metastore, even
> though it's not running.
> Note: For reference, I added a second HiveServer2, and it made two alert
> instances and one showed OK and the other CRIT because the HiveServer2 was
> not running. So this worked fine for the HiveServer2. Just seems the Hive
> Metastore alerts didn't adjust properly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
