hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6293) Issues with OIV processing PB-based fsimages
Date Mon, 12 May 2014 21:38:17 GMT

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

Suresh Srinivas commented on HDFS-6293:
---------------------------------------

I agree with [~kihwal] on deprecation. Is this also going into trunk? I think first it should
be committed to trunk and then branch-2. If we are in a position to remove it from trunk later,
then it can be removed later. Thoughts?

+1 for the patch with Jenkins +1 (if it is going to trunk as well).

> Issues with OIV processing PB-based fsimages
> --------------------------------------------
>
>                 Key: HDFS-6293
>                 URL: https://issues.apache.org/jira/browse/HDFS-6293
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 2.4.0
>            Reporter: Kihwal Lee
>            Assignee: Haohui Mai
>            Priority: Blocker
>         Attachments: HDFS-6293.000.patch, HDFS-6293.001.patch, HDFS-6293.002-save-deprecated-fsimage.patch,
HDFS-6293_sbn_ckpt_retention.patch, HDFS-6293_sbn_ckpt_retention_oiv_legacy.patch, Heap Histogram.html
>
>
> There are issues with OIV when processing fsimages in protobuf. 
> Due to the internal layout changes introduced by the protobuf-based fsimage, OIV consumes
excessive amount of memory.  We have tested with a fsimage with about 140M files/directories.
The peak heap usage when processing this image in pre-protobuf (i.e. pre-2.4.0) format was
about 350MB.  After converting the image to the protobuf format on 2.4.0, OIV would OOM even
with 80GB of heap (max new size was 1GB).  It should be possible to process any image with
the default heap size of 1.5GB.
> Another issue is the complete change of format/content in OIV's XML output.  I also noticed
that the secret manager section has no tokens while there were unexpired tokens in the original
image (pre-2.4.0).  I did not check whether they were also missing in the new pb fsimage.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message