[
https://issues.apache.org/jira/browse/HDFS-12328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16136223#comment-16136223
]
Yiqun Lin commented on HDFS-12328:
----------------------------------
Hi [~yuanbo] and [~cheersyang], just some thoughts from me:
Should we must reset count to -1 after max retry times? Can we add a prefix
like {{#corrupted#}} in block key that indicated this block is corrupted block
and should be deleted in a manual way. It would be better to display the
corrupted block number in JMX that will be aware by users. But this work can be
done in the following JIRA.
> Ozone: Purge metadata of deleted blocks after max retry times
> -------------------------------------------------------------
>
> Key: HDFS-12328
> URL: https://issues.apache.org/jira/browse/HDFS-12328
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Yuanbo Liu
> Assignee: Yuanbo Liu
>
> In HDFS-12283, we set the value of count to -1 if blocks cannot be deleted
> after max retry times. We need to provide APIs for admins to purge the "-1"
> metadata manually.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
