[
https://issues.apache.org/jira/browse/HDFS-11626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15960871#comment-15960871
]
Kihwal Lee commented on HDFS-11626:
-----------------------------------
bq. oiv_legacy only works for fsimage at or before Hadoop 2.4.
We still support saving fsimage in the old writable format. This is of course
only for analysis purposes, not meant for namenode consumption. If we decide to
deprecate the tool, we might as well deprecate this capability. This format
was kept because the memory requirement for processing it was low and
independent of the size of the namespace. Often 128MB of heap is all it needs.
The processing of PB format is not feasible if it requires over 10s of GB for a
large name space we have. There are later improvements, but it still is
inefficient compared to the writable-based image processing.
If the future of human race depends on ditching this, we would deprecate it in
3 and remove it in 4.
> Deprecate oiv_legacy tool
> -------------------------
>
> Key: HDFS-11626
> URL: https://issues.apache.org/jira/browse/HDFS-11626
> Project: Hadoop HDFS
> Issue Type: Task
> Components: tools
> Reporter: Wei-Chiu Chuang
>
> oiv_legacy only works for fsimage at or before Hadoop 2.4. I think we can
> deprecate oiv_legacy in Hadoop 3 in preparation for final removal in Hadoop 4.
> Or would people favor removing it in Hadoop 3?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
