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 "Arpit Agarwal (JIRA)" <ji...@apache.org> on 2018/05/08 22:29:00 UTC

[jira] [Moved] (HDDS-35) DiskChecker should handle disk full situation

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

Arpit Agarwal moved HADOOP-15451 to HDDS-35:
--------------------------------------------

    Target Version/s:   (was: 3.1.1, 2.9.2, 3.0.3, 2.8.5)
            Workflow: patch-available, re-open possible  (was: no-reopen-closed, patch-avail)
                 Key: HDDS-35  (was: HADOOP-15451)
             Project: Hadoop Distributed Data Store  (was: Hadoop Common)

> DiskChecker should handle disk full situation
> ---------------------------------------------
>
>                 Key: HDDS-35
>                 URL: https://issues.apache.org/jira/browse/HDDS-35
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>            Reporter: Kihwal Lee
>            Assignee: Arpit Agarwal
>            Priority: Blocker
>
> Fix disk checker issues reported by [~kihwal] in HADOOP-13738:
> When space is low, the os returns ENOSPC. Instead simply stop writing, the drive is marked bad and replication happens. This make cluster-wide space problem worse. If the number of "failed" drives exceeds the DFIP limit, the datanode shuts down.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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