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

Hudson commented on AMBARI-20818:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1444 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1444/])
AMBARI-20818. Blueprint processor fails when StackAdvisor recommends (smagyari: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9583ede2aef55646dc2c11dc03648cee966258ba])
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/api/services/stackadvisor/StackAdvisorBlueprintProcessorTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/topology/ClusterDeployWithStartOnlyTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/topology/ClusterConfigurationRequestTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/topology/ClusterInstallWithoutStartOnComponentLevelTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/api/services/stackadvisor/StackAdvisorBlueprintProcessor.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/topology/ClusterInstallWithoutStartTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/topology/ClusterConfigurationRequest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/topology/BlueprintImpl.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/topology/Blueprint.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java


> Blueprint processor fails when StackAdvisor recommends unnecessary 
> configuration types
> --------------------------------------------------------------------------------------
>
>                 Key: AMBARI-20818
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20818
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Sandor Magyari
>            Assignee: Sandor Magyari
>            Priority: Critical
>             Fix For: 3.0.0
>
>         Attachments: AMBARI-20818.patch, AMBARI-20818-v2.patch
>
>
> When deploying a minimal Blueprint, that only included the Hive 
> MetaStoreServer and Zookeeper, without any other services the deployment 
> failed, and was stuck in the "PENDING" state.  
> The root cause is the following exception in ambari-server.log:
> {code}
> java.lang.NullPointerException
>         at 
> org.apache.ambari.server.topology.AmbariContext.waitForConfigurationResolution(AmbariContext.java:430)
>         at 
> org.apache.ambari.server.topology.ClusterConfigurationRequest.setConfigurationsOnCluster(ClusterConfigurationRequest.java:496)
>         at 
> org.apache.ambari.server.topology.ClusterConfigurationRequest.setConfigurationsOnCluster(ClusterConfigurationRequest.java:406)
>         at 
> org.apache.ambari.server.topology.ClusterConfigurationRequest.process(ClusterConfigurationRequest.java:159)
>         at org.apache.ambari.server.topology.tasks.
> {code}
> The problem is that Blueprints processor receives some configuration 
> recommendations from the StackAdvisor for "yarn-site" and "yarn-env", even 
> though Yarn is not present in the cluster. This causes the Blueprint 
> processor to treat these types as updated, and will eventually cause the 
> NullPointerException I mentioned above.
> This causes the cluster configuration to be in an inconsistent state, and the 
> Blueprint deployment won't necessarily complete properly, although some 
> manual configuration changes would likely result in a working cluster.
> The Blueprint processor should be updated to ignore any configuration types 
> recommended by the StackAdvisor that are not needed for the current cluster.  
> Usually, these types are from services that are not selected for the cluster. 
>  
> If a recommendation is present for a configuration type that is not included 
> in the "desired configurations" for a cluster, the Blueprint processor should 
> ignore this configuration type, and perhaps log some time of warning, so that 
> the user is aware that some recommendations were made that are not being 
> used.  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to