ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hari Sekhon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-21495) Shows only warnings against all nodes hiding cause when service fails to bootstrap/start (eg. Schema Registry, Ranger admin) on HDF 3.0 cluster install
Date Wed, 19 Jul 2017 07:28:00 GMT

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

Hari Sekhon commented on AMBARI-21495:
--------------------------------------

This also happens when adding Ranger service and Ranger admin fails to start, the node shows
warning only, but clicking on the warning shows an error status, which is inconsistent behaviour,
adding a couple new screenshots to demonstrate.

> Shows only warnings against all nodes hiding cause when service fails to bootstrap/start
(eg. Schema Registry, Ranger admin) on HDF 3.0 cluster install
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-21495
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21495
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.5.1
>         Environment: HDF 3.0
>            Reporter: Hari Sekhon
>         Attachments: Ambari_all_warnings.png, Ambari_all_warnings_random_services2.png,
Ambari_all_warnings_random_services3.png, Ambari_all_warnings_random_services4_culprit.png,
Ambari_all_warnings_random_services.png, Ambari_post_install_shows_the_failure_correctly.png
>
>
> Ambari marks all nodes with warnings including component failure which should have been
shown as red failure.
> This was caused by a failure to bootstrap the Registry Schema (AMBARI-21492), but Ambari
showed only warnings against all cluster hosts, while each host had a blank warning against
random components where it had aborted but there was nothing wrong with those components so
no error outputs.
> The failure during Registry Startup bootstrap script should have been shown as red failure
not yellow warning as the only way I could find the root cause was to go through the nodes
one by one, which luckily this is a small 9 node cluster a not a 50 - 100+ cluster as I might
not have found it otherwise.
> Post cluster install the Ops screen does show the red failure correctly, this appears
to only be a bug with the cluster installer.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message