Chapter 13. Tuning Ambari Performance

For clusters larger than 200 nodes, consider the following tuning options:

Calculate the new, larger cache size, using the following relationship:
ecCacheSizeValue=60*<cluster_size>
where <cluster_size> is the number of nodes in the cluster.
On the Ambari Server host, in /etc/ambari-server/conf/ambari-properties, add the following property and value:
server.ecCacheSize=<ecCacheSizeValue>
where <ecCacheSizeValue> is the value calculated previously, based on the number of nodes in the cluster.
Add the following properties to adjust the JDBC connection pool settings:
server.jdbc.connection-pool.acquisition-size=5
server.jdbc.connection-pool.max-age=0
server.jdbc.connection-pool.max-idle-time=14400
server.jdbc.connection-pool.max-idle-time-excess=0
server.jdbc.connection-pool.idle-test-interval=7200
If using MySQL as the Ambari database, increase the timeout in MySQL from 15 minutes to 8 hours and the max connections from 32 to 128.
Restart Ambari Server.
ambari-server restart
If you are using the Ambari Metrics service, you might want to consider switching from the default embedded mode to distributed mode, as well as other tuning options. See Advanced Configurations for Ambari Metrics for more information.