[
https://issues.apache.org/jira/browse/HDFS-17528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17854249#comment-17854249
]
ASF GitHub Bot commented on HDFS-17528:
---------------------------------------
ayushtkn commented on PR #6828:
URL: https://github.com/apache/hadoop/pull/6828#issuecomment-2162103444
you can ignore that test failure, I have dropped a comment on the original
ticket which caused that, it is failing in our daily build as well.
The previous build crashing was due to the surefire-upgrade which is
reverted, there is a thread on hdfs-dev@ about it
> FsImageValidation: set txid when saving a new image
> ---------------------------------------------------
>
> Key: HDFS-17528
> URL: https://issues.apache.org/jira/browse/HDFS-17528
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: tools
> Reporter: Tsz-wo Sze
> Assignee: Tsz-wo Sze
> Priority: Major
> Labels: pull-request-available
>
> - When the fsimage is specified as a file and the FsImageValidation tool
> saves a new image (for removing inaccessible inodes), the txid is not set.
> Then, the resulted image will have 0 as its txid.
> - When the fsimage is specified as a directory, the txid is set. However, it
> will get NPE since NameNode metrics is uninitialized (although the metrics is
> not used by FsImageValidation).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
