[
https://issues.apache.org/jira/browse/AMBARI-18390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-18390:
---------------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to branch-2.4 and trunk.
> Configuration warnings during "Add Service" Wizard includes seemingly
> nonsensical heapsize recommendations
> ----------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-18390
> URL: https://issues.apache.org/jira/browse/AMBARI-18390
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.4.0
> Environment: SLES11 SP3
> Reporter: Zack Marsh
> Assignee: Aravindan Vijayan
> Fix For: 2.4.2
>
> Attachments: AMBARI-18390.patch, Ambari_Metrics_Warnings_1.png,
> Ambari_Metrics_Warnings_2.png, Ambari_Metrics_Warnings_3.png, log.zip
>
>
> On an HDP 2.5.0.0 + Ambari 2.4.0.1 cluster, I'm prompted with
> misconfiguration warnings while adding a service (e.g. Kafka in this case).
> {code}
> Warning, Ambari Metrics, hbase_master_heapsize, 896
> 246061 MB RAM is unused on the host zeus.labs.teradata.com based on
> components assigned.
> Consider allocating 48905 MB to metrics_collector_heapsize in ams-env, 32768
> MB to hbase_master_heapsize in ams-hbase-env
> HBase Master Heap Size. In embedded mode, total heap size is sum of master
> and regionserver heap sizes.
> {code}
> {code}
> Warning, Ambari Metrics, hbase_master_xmn_size, 256
> Consider allocating 3968 MB to use up some unused memory on host
> HBase Master maximum value for young generation heap size.
> {code}
> See attached file Ambari_Metrics_Warnings_1.png for a screenshot of Ambari's
> warnings.
> So per the recommendations, I set:
> * metrics_collector_heapsize = 48905 MB
> * hbase_master_heapsize = 32768 MB
> * hbase_master_xmn_size = 3968 MB
> Saved changes and restarted Ambari Metrics.
> Now when I try adding a service again, I'm prompted with the following
> warnings:
> {code}
> Warning, Ambari Metrics, hbase_master_heapsize, 32768
> 165796 MB RAM is unused on the host zeus1.labs.teradata.com based on
> components assigned. Consider allocating 81245 MB to
> metrics_collector_heapsize in ams-env, 32768 MB to hbase_master_heapsize in
> ams-hbase-env
> HBase Master Heap Size. In embedded mode, total heap size is sum of master
> and regionserver heap sizes.
> {code}
> {code}
> Warning, Ambari Metrics, hbase_master_xmn_size, 3968
> Value is lesser than the recommended minimum Xmn size of 4025 (12% of
> hbase_master_heapsize + hbase_regionserver_heapsize)
> Consider allocating 3968 MB to use up some unused memory on host
> HBase Master maximum value for young generation heap size.
> {code}
> See attached file Ambari_Metrics_Warnings_2.png for a screenshot of Ambari's
> warnings.
> Set:
> * metrics_collector_heapsize = 81245 MB
> * hbase_master_xmn_size = 4025 MB
> Saved changes and restarted Ambari Metrics.
> Now when I try adding a service for a third time, I'm prompted with the
> following warnings:
> {code}
> Warning, Ambari Metrics, hbase_master_heapsize, 32768
> 133456 MB RAM is unused on the host zeus1.labs.teradata.com based on
> components assigned. Consider allocating 107117 MB to
> metrics_collector_heapsize in ams-env, 32768 MB to hbase_master_heapsize in
> ams-hbase-env
> HBase Master Heap Size. In embedded mode, total heap size is sum of master
> and regionserver heap sizes.
> {code}
> {code}
> Warning, Ambari Metrics, hbase_master_xmn_size, 4025
> Consider allocating 3968 MB to use up some unused memory on host
> HBase Master maximum value for young generation heap size.
> {code}
> See attached file Ambari_Metrics_Warnings_3.png for a screenshot of Ambari's
> warnings.
> At this point I stopped because the recommended settings were already
> non-sensical.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
