hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-15450) Avoid fsync storm triggered by DiskChecker and handle disk full situation
Date Mon, 07 May 2018 19:32:00 GMT

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

Jason Lowe updated HADOOP-15450:
--------------------------------
    Target Version/s: 2.8.4, 3.1.1, 2.9.2, 3.0.3
       Fix Version/s:     (was: 2.8.4)

> Avoid fsync storm triggered by DiskChecker and handle disk full situation
> -------------------------------------------------------------------------
>
>                 Key: HADOOP-15450
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15450
>             Project: Hadoop Common
>          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.
> # There are non-hdfs users of DiskChecker, who use it proactively, not just on failures.
This was fine before, but now it incurs heavy I/O due to introduction of fsync() in the code.



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

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


Mime
View raw message