Cluster tuning parameters for provisioning Ambari-managed HDP Cluster via blueprint

[#1]

I have used a blueprint to provision an HDP cluster in the following conditions:

- Create an Ambari-managed HDP cluster in a manual approach (Non-blueprint installation)

- Extract blueprint from the created cluster.

- Remove all non-generic parts and all tuning part from the extracted blueprint to make it more generic.

- Create host-group mapping file to capture all passwords and hostnames.

- Create another cluster with the modified blueprint and host-group mapping file.

My question is when you are using a manual installation Ambari selects the recommended values for tuning parameters. However, in the blueprint installation, you need to modify them separately or put all parameters in host-group mapping file which make the blueprint maintenance very hard. I was wondering whether there is another way that Ambari can pick all the parameters in the same way that is used in a Non-blueprint installation.

[#2 · Accepted solution]

Hi @Ali,

There is a way to have the Blueprints processor apply the Ambari Server recommendations for configuration for various services. In Ambari 2.2.0, Blueprints was updated to provide integration with the StackAdvisor/Recommendations engine.

Basically, adding some configuration in the cluster creation template will instruct the Blueprints processor to apply the output of the recommendations engine.

There are various strategies that can be applied, based on the desired outcome. By default, the strategy is "NEVER_APPLY", which means that recommendations are not applied by default. This was done to ensure backwards compatibility, as the Blueprints processor preceded the StackAdvisor implementation in Ambari.

Here's a link to the configuration you'll need to add to your cluster creation template if you'd like to have Blueprints apply the recommendations automatically:

https://cwiki.apache.org/confluence/display/AMBARI/Blueprints#Blueprints-ClusterCreationTemplateStru...

The "config_recommendation_strategy" property needs to be added to the cluster creation template, and set to one of the supported strategies.

This should allow you to make your Blueprint smaller and more portable, since the recommended values do not need to be set, unless you prefer to override the values set by the recommendations engine.

Hope this helps.

Thanks,

Bob

[#3]

Briliant. Thanks.