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

Kihwal Lee commented on HDFS-6293:
----------------------------------

bq. ....can you please mark the class that are brought back deprecated?
I am not sure deprecating it now is a good idea.  There are two apsects in this.
* Ability to read the old fsimage format in OIV. This has always been the case 
for OIV. Now it will be the combination of oiv and oiv_legacy that will 
continue this.   As long as NN can read/upgrade old images, there is no reason 
to hurry and remove this capability from oiv.
* Support for the use case built around the old oiv.  Users won't care much 
about the image format as long as they can obtain what they want, using 
reasonable and comparable amount of resources as before.  If we only think 
about this, we can deprecate OIV and NN's ability to save the old format, once 
we have a long term alternative solution.


> 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)

Reply via email to