[
https://issues.apache.org/jira/browse/HADOOP-15450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16483469#comment-16483469
]
Yongjun Zhang commented on HADOOP-15450:
----------------------------------------
Hi [~arpitagarwal],
Thanks for working on this issue.
I'm preparing for 3.0.3 release. Couple of questions:
1. This jira seems an important one, would you please confirm it's a blocker
for 3.0.3?
2. If it's a blocker, do we need HDFS-13538 too?
{quote}
Split this out into separate changes. For now this fixes Hadoop Common to avoid
doing disk IO unless explicitly requested to address the immediate concern.
Will add the disk full check via HDFS-13538.
{quote}
Thanks.
> 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: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
