a70a74aa23
Group the existing pages in the new top-level categories; each category can be seen as a separate document and it has its own index file. The content of the pages was not changed, with the obvious exception of the links between pages. The autogenerated configuration has not been added yet to configuration/; it will be fixed in a future commit. At the same time, as suggested by the doc team, consistently use only one separator in file names (dash, '-') instead of a mix of dashes, dots and underscores. This may break even more links on the Internet, but we are breaking them anyway by moving files. Redirects can be set, but not in this commit. Closes-Bug: #1706184 Change-Id: I5a10378d9da2603d617ad4193ea8d90e2afc5104
1.9 KiB
- orphan
Autoconfiguring templates
During the Liberty development cycle sahara implemented a tool that recommends and applies configuration values for cluster templates and node group templates. These recommendations are based on the number of specific instances and on flavors of the cluster node groups. Currently the following plugins support this feature:
- CDH;
- Ambari;
- Spark;
- the Vanilla Apache Hadoop plugin.
By default this feature is enabled for all cluster templates and node
group templates. If you want to disable this feature for a particular
cluster or node group template you should set the
use_autoconfig field to false.
The following describes the settings for which sahara can recommend autoconfiguration:
The Cloudera, Spark and Vanilla Apache Hadoop plugin support
configuring dfs.replication (dfs_replication
for Cloudera plugin) which is calculated as a minimum from the amount of
datanode (HDFS_DATANODE for Cloudera plugin)
instances in the cluster and the default value for
dfs.replication.
The Vanilla Apache Hadoop plugin and Cloudera plugin support autoconfiguration of basic YARN and MapReduce configs. These autoconfigurations are based on the following documentation: http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.0.9.1/bk_installing_manually_book/content/rpm-chap1-11.html
The Ambari plugin has its own strategies on configuration
recommendations. You can choose one of ALWAYS_APPLY,
NEVER_APPLY, and ONLY_STACK_DEFAULTS_APPLY. By
default the Ambari plugin follows the NEVER_APPLY strategy.
You can get more information about strategies in Ambari's official
documentation: https://cwiki.apache.org/confluence/display/AMBARI/Blueprints#Blueprints-ClusterCreationTemplateStructure