You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Rohini Palaniswamy (JIRA)" <ji...@apache.org> on 2015/06/12 22:04:00 UTC
[jira] [Commented] (PIG-3251) Bzip2TextInputFormat requires double
the memory of maximum record size
[ https://issues.apache.org/jira/browse/PIG-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583985#comment-14583985 ]
Rohini Palaniswamy commented on PIG-3251:
-----------------------------------------
Had a discussion with [~knoguchi]. He was suggesting that we should probably start with using hadoop's TextInputFormat for bzip2 processing as a option based on configuration. After more stabilization, can make it default. Agree with that idea.
I also noticed that there is one open issue with concatenated bzip support in hadoop - HADOOP-6852. Since we have not supported concatenated gzip at all so far with the Pig's bzip implementation, that should be ok.
> Bzip2TextInputFormat requires double the memory of maximum record size
> ----------------------------------------------------------------------
>
> Key: PIG-3251
> URL: https://issues.apache.org/jira/browse/PIG-3251
> Project: Pig
> Issue Type: Improvement
> Reporter: Koji Noguchi
> Assignee: Koji Noguchi
> Priority: Minor
> Attachments: pig-3251-trunk-v01.patch, pig-3251-trunk-v02.patch, pig-3251-trunk-v03.patch, pig-3251-trunk-v04.patch, pig-3251-trunk-v05.patch
>
>
> While looking at user's OOM heap dump, noticed that pig's Bzip2TextInputFormat consumes memory at both
> Bzip2TextInputFormat.buffer (ByteArrayOutputStream)
> and actual Text that is returned as line.
> For example, when having one record with 160MBytes, buffer was 268MBytes and Text was 160MBytes.
> We can probably eliminate one of them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)