[
https://issues.apache.org/jira/browse/HADOOP-15450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16484137#comment-16484137
]
Arpit Agarwal commented on HADOOP-15450:
----------------------------------------
[~kihwal], can you review this patch? I believe it will address your concerns
for now. It solves the immediate problem by removing disk IO from the disk
check path.
HDFS-13538 is the second part of the change to restore disk IO for HDFS disk
checks but also add an exception for disk full. That should not block any
releases.
> 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
> Attachments: HADOOP-15450.01.patch, HADOOP-15450.02.patch
>
>
> Fix disk checker issues reported by [~kihwal] in HADOOP-13738
> 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: [email protected]
For additional commands, e-mail: [email protected]
