ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandor Magyari (JIRA)" <>
Subject [jira] [Updated] (AMBARI-20818) Blueprint processor fails when StackAdvisor recommends unnecessary configuration types
Date Fri, 21 Apr 2017 18:08:04 GMT


Sandor Magyari updated AMBARI-20818:
    Status: Patch Available  (was: Open)

> Blueprint processor fails when StackAdvisor recommends unnecessary configuration types
> --------------------------------------------------------------------------------------
>                 Key: AMBARI-20818
>                 URL:
>             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(
>         at org.apache.ambari.server.topology.ClusterConfigurationRequest.setConfigurationsOnCluster(
>         at org.apache.ambari.server.topology.ClusterConfigurationRequest.setConfigurationsOnCluster(
>         at org.apache.ambari.server.topology.ClusterConfigurationRequest.process(
>         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

View raw message