You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Steve Loughran (Jira)" <ji...@apache.org> on 2022/04/12 11:48:00 UTC

[jira] [Updated] (HDFS-16501) Print the exception when reporting a bad block

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

Steve Loughran updated HDFS-16501:
----------------------------------
    Target Version/s: 3.3.3

> Print the exception when reporting a bad block
> ----------------------------------------------
>
>                 Key: HDFS-16501
>                 URL: https://issues.apache.org/jira/browse/HDFS-16501
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: datanode
>            Reporter: qinyuren
>            Assignee: qinyuren
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.4.0, 3.2.4, 3.3.4
>
>         Attachments: image-2022-03-10-19-27-31-622.png
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> !image-2022-03-10-19-27-31-622.png|width=847,height=27!
> Currently, volumeScanner will find bad block and report it to namenode without printing the reason why the block is a bad block. I think we should be better print the exception in log file.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org