[
https://issues.apache.org/jira/browse/AMBARI-10602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504732#comment-14504732
]
Hudson commented on AMBARI-10602:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #2385 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2385/])
AMBARI-10602 HDFS namenode_opt_newsize and namenode_opt_maxnewsize not using
number of datanodes in calculation (dsen) (dsen:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c3e0771e40fb255ff69bb6cbc70495435486512e)
* ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py
* ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py
* ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py
* ambari-server/src/test/python/stacks/2.0.6/common/test_stack_advisor.py
> HDFS namenode_opt_newsize and namenode_opt_maxnewsize not using number of
> datanodes in calculation
> --------------------------------------------------------------------------------------------------
>
> Key: AMBARI-10602
> URL: https://issues.apache.org/jira/browse/AMBARI-10602
> Project: Ambari
> Issue Type: Bug
> Components: stacks
> Affects Versions: 2.1.0
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Fix For: 2.1.0
>
> Attachments: AMBARI-10602.patch
>
>
> Reviewing HDFS recommendation code for namenode_heapsize,
> namenode_opt_newsize and namenode_opt_maxnewsize, it looks like the
> calculations are not taking into account the number of datanodes and disks
> per datanode.
> HDFS recommendations currently gives the following output
> {code}
> "configurations": {
> "hadoop-env": {
> "properties": {
> "namenode_heapsize": "1024",
> "namenode_opt_maxnewsize": "256",
> "namenode_opt_newsize": "256"
> },
> "property_attributes": {
> "namenode_heapsize": {
> "maximum": "2887"
> },
> "dtnode_heapsize": {
> "maximum": "2887"
> }
> }
> },
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
