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 "Xiaoqiao He (Jira)" <ji...@apache.org> on 2024/04/18 13:43:00 UTC
[jira] [Commented] (HDFS-17483) volume in full disk will be regarded as failure volume when dn restart
[ https://issues.apache.org/jira/browse/HDFS-17483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17838661#comment-17838661 ]
Xiaoqiao He commented on HDFS-17483:
------------------------------------
[~Xuze Yang] Thanks for your report. Would you mind to submit patch via GitHub? Thanks.
> volume in full disk will be regarded as failure volume when dn restart
> ----------------------------------------------------------------------
>
> Key: HDFS-17483
> URL: https://issues.apache.org/jira/browse/HDFS-17483
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 3.3.5
> Reporter: Xuze Yang
> Priority: Major
> Attachments: 0001-HDFS-17483-volume-in-full-disk-will-be-regarded-as-f.patch
>
>
> When DN restart, tmpDir will first deleted then created. If disk is full, create tmpDir will fail. As a result, the correponding volume will be added to failure volumes.
> Additionaly, the file in-use.lock has the same behaviour. (deleted when dn shutdown, created when dn restarted)
--
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