[
https://issues.apache.org/jira/browse/AMBARI-20818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15979743#comment-15979743
]
Hadoop QA commented on AMBARI-20818:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12864540/AMBARI-20818.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.topology.ClusterInstallWithoutStartTest
org.apache.ambari.server.topology.ClusterDeployWithStartOnlyTest
org.apache.ambari.server.state.UpgradeHelperTest
org.apache.ambari.server.topology.ClusterInstallWithoutStartOnComponentLevelTest
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11455//console
This message is automatically generated.
> 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
>
>
> 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)
