Description
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.
Attachments
Attachments
Issue Links
- breaks
-
HDFS-6419 TestBookKeeperHACheckpoints#TestSBNCheckpoints fails on trunk
- Closed
- is blocked by
-
HDFS-6914 Resolve huge memory consumption Issue with OIV processing PB-based fsimages
- Patch Available
- is related to
-
HDFS-6673 Add delimited format support to PB OIV tool
- Closed
-
HDFS-11709 StandbyCheckpointer should handle an non-existing legacyOivImageDir gracefully
- Resolved
-
HDFS-6400 Cannot execute "hdfs oiv_legacy"
- Closed
- relates to
-
HDFS-6310 PBImageXmlWriter should output information about Delegation Tokens
- Patch Available
-
HDFS-6519 Document oiv_legacy command
- Closed
1.
|
Support protobuf-based directory listing output suitable for OIV | Open | Unassigned | |
2.
|
REST API for fetching directory listing file from NN | Open | Unassigned |