ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] [Commented] (AMBARI-14664) Blueprints: After Kerberos deployment, UI requires that Yarn service be restarted
Date Thu, 14 Jan 2016 22:12:40 GMT


Hudson commented on AMBARI-14664:

FAILURE: Integrated in Ambari-branch-2.2 #200 (See [])
AMBARI-14664. Blueprints: After Kerberos deployment, UI requires that (rnettleton: [])
* ambari-server/src/main/java/org/apache/ambari/server/controller/
* ambari-server/src/test/java/org/apache/ambari/server/topology/
* ambari-server/src/main/java/org/apache/ambari/server/topology/

> Blueprints: After Kerberos deployment, UI requires that Yarn service be restarted
> ---------------------------------------------------------------------------------
>                 Key: AMBARI-14664
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.2.0
>            Reporter: Sandor Magyari
>            Assignee: Sandor Magyari
>            Priority: Critical
>             Fix For: 2.2.1
>         Attachments: AMBARI-14664.patch
> This is similar issue to AMBARI-14251 Stale configuration problem.
> Kerberos.json config files contains a few properties like: {$clusterHostInfo/webhcat_server_host}
for HIVE and KNOX configs. These properties are replaced using StageUtils.getClusterHostInfo()
which is a quite problematic one and sometimes could happen that hosts are missing from clusterHostInfo
since TopologyHostRequest were not created at that time.
> The solution would be to pass clusterHostInfo map to KerberosHelper in case of using
it from TopologyManager so there's no need to get clusterInfo from StageUtils. We can create
this map from ClusterTopology once topology is resolved. To retrieve hosts to be resolved
form kerberos configs, we would pass an empty componentHostMap then we can select host variables
from config properties. This way the same Kerberos config logic will run both for BP and non
BP deployments.

This message was sent by Atlassian JIRA

View raw message