[jira] [Updated] (HDFS-17528) FsImageValidation: set txid when saving a new image

["Wei-Chiu Chuang (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HDFS-17528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wei-Chiu Chuang updated HDFS-17528:
-----------------------------------
    Fix Version/s: 3.4.3

> 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
>             Fix For: 3.5.0, 3.4.3
>
>
> - 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: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org