hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "nijel (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-6343) JobConf.parseMaximumHeapSizeMB() fails to parse value greater than 2GB expressed in bytes
Date Tue, 28 Apr 2015 02:44:06 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14516225#comment-14516225
] 

nijel commented on MAPREDUCE-6343:
----------------------------------

Hi
Casting to integer may not be a good idea, because the user might expect the same heap as
he configured but actually not.
It will be good if the variable is changed to long at the earliest at least in trunk.
Since java support configuring the mx in bytes, it will be good if mapreduce framework can
support the big values


> JobConf.parseMaximumHeapSizeMB() fails to parse value greater than 2GB expressed in bytes
> -----------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-6343
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6343
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 3.0.0
>            Reporter: Hao Xia
>         Attachments: parse-heap-size.patch
>
>
> It currently tries to parse the value as an integer, which blows up whenever the value
is greater than 2GB and expressed in bytes.



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

Mime
View raw message