[
https://issues.apache.org/jira/browse/HADOOP-11098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14941277#comment-14941277
]
Tsz Wo Nicholas Sze commented on HADOOP-11098:
----------------------------------------------
On a second thought, Long.MAX_VALUE = 9223372036854775807 has too many digits.
It may lead to a display problem. Also, other applications cannot easily tell
whether it means unbounded or it is a valid setting. They cannot show it as
<unbounded> in their UI. So -1 may be better.
> [JDK8] Max Non Heap Memory default changed between JDK7 and 8
> -------------------------------------------------------------
>
> Key: HADOOP-11098
> URL: https://issues.apache.org/jira/browse/HADOOP-11098
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 2.3.0, 2.7.1
> Environment: JDK8
> Reporter: Travis Thompson
>
> I noticed this because the NameNode UI shows "Max Non Heap Memory" which
> after some digging I found correlates to MaxDirectMemorySize.
> JDK7
> {noformat}
> Heap Memory used 16.75 GB of 23 GB Heap Memory. Max Heap Memory is 23.7 GB.
> Non Heap Memory used 57.32 MB of 67.38 MB Commited Non Heap Memory. Max Non
> Heap Memory is 130 MB.
> {noformat}
> JDK8
> {noformat}
> Heap Memory used 3.02 GB of 7.65 GB Heap Memory. Max Heap Memory is 23.7 GB.
> Non Heap Memory used 103.12 MB of 104.41 MB Commited Non Heap Memory. Max Non
> Heap Memory is -1 B.
> {noformat}
> More information in first comment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
