[
https://issues.apache.org/jira/browse/AMBARI-9655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14322289#comment-14322289
]
Hudson commented on AMBARI-9655:
--------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #1778 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/1778/])
AMBARI-9655. Added Second Hive Metastore, two alert instances but both OK
(alexantonenko) (hiveww:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=bff7124bb934005cee93c13cd93226bb9c1609ea)
* ambari-web/app/controllers/main/service/item.js
* ambari-web/app/utils/components.js
* ambari-web/app/controllers/main/host/details.js
> 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)
