ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-14251) Blueprints: fix stale configs and kerberos-env stack defaults are not being applied during cluster deployment
Date Wed, 09 Dec 2015 01:48:10 GMT

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

Hudson commented on AMBARI-14251:
---------------------------------

SUCCESS: Integrated in Ambari-branch-2.2 #39 (See [https://builds.apache.org/job/Ambari-branch-2.2/39/])
AMBARI-14251. Blueprints fix stale configs and kerberos-env stack (rnettleton: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b1149fa7e827c94ab929a25b9b7f9bc6165b8605])
* ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementController.java
* ambari-server/src/main/java/org/apache/ambari/server/topology/TopologyManager.java
* ambari-server/src/test/java/org/apache/ambari/server/topology/ClusterConfigurationRequestTest.java
* ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* ambari-server/src/main/java/org/apache/ambari/server/topology/ClusterConfigurationRequest.java


> Blueprints: fix stale configs and kerberos-env stack defaults are not being applied during
cluster deployment
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-14251
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14251
>             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.0
>
>         Attachments: AMBARI-14251.patch
>
>
> The following issues were discovered during Kerberized cluster deployment using Blueprints:
> 1. Stale configuration problem: Kerberos related configuration is generated for each
host separately but applied on the whole Cluster. In case two components having common config
types (like core-site in case of YARN_CLIENT and RESOURCEMANAGER) are deployed on two different
hosts, Kerberos configuration changes generated by one host may interfere with config types
deployed on other host. Eg. host2 modifies properties in core-site for RESOURCEMANAGER when
same config type is already pushed to host1, causing Ambari to consider host1 with steal config.
  
> 2. Stack default values for properties in kerberos-env and krb5-conf are not being applied
during cluster deployment in case they are defined only in Cluster create template configurations




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message