ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hari Sekhon (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-10732) Ambari recommending huge NameNode heap size increase after HDFS storage tiering
Date Fri, 24 Apr 2015 16:08:38 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-10732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hari Sekhon updated AMBARI-10732:
---------------------------------
    Summary: Ambari recommending huge NameNode heap size increase after HDFS storage tiering
 (was: Ambari recommending huge NameNode heap size increase?)

> Ambari recommending huge NameNode heap size increase after HDFS storage tiering
> -------------------------------------------------------------------------------
>
>                 Key: AMBARI-10732
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10732
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>         Environment: HDP 2.2
>            Reporter: Hari Sekhon
>            Priority: Minor
>         Attachments: Ambari recommending massive NameNode Heap.png
>
>
> After adding an HDFS storage tiering configuration, on saving it Ambari suddenly recommends
the configuration of the NameNode heap be drastically increased from around 3GB to 51GB, even
though the archive tier only adds 1/5 of the capacity compared to the already configured local
disk and the NameNode heap is only 65% used right now.
> This seems like a calculation bug, so I've ignored that recommendation and may increase
the NameNode heap to a more sensible 4-5GB if needed.
> I'm attaching a screenshot.
> Hari Sekhon
> http://www.linkedin.com/in/harisekhon



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message