[ https://issues.apache.org/jira/browse/AMBARI-18089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Hurley updated AMBARI-18089: ------------------------------------- Status: Patch Available (was: Open) > Create Documentation Around All Options In ambari.properties > ------------------------------------------------------------ > > Key: AMBARI-18089 > URL: https://issues.apache.org/jira/browse/AMBARI-18089 > Project: Ambari > Issue Type: Task > Components: ambari-server > Affects Versions: 2.4.0 > Reporter: Jonathan Hurley > Assignee: Jonathan Hurley > Priority: Critical > Fix For: 2.5.0 > > > Ambari Server has "sensible" defaults for many of the configurations in > {{ambari.properties}}. They may work for 5-, 10-, 50-, or even 100-host > clusters. However, they _must_ be properly tuned in any situation which has a > large, production-level topology. > There is currently sparse to no documentation on many of these properties. > For every property, we need to consider: > - The context in which different cluster deployments could be affected by it > -- Cluster Size > -- Cluster History > -- Concurrent Users > - Provide recommendations that are grouped logically, such as (for example) > -- Multiple Concurrent Users > -- 50 to 100 Hosts > -- Ambari Server Hardware -- This message was sent by Atlassian JIRA (v6.3.4#6332)