[
https://issues.apache.org/jira/browse/HADOOP-15450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16484048#comment-16484048
]
Kihwal Lee commented on HADOOP-15450:
-------------------------------------
Yes it is a blocker. The performance regression was introduced in HADOOP-13738.
For the 2.8.4 release, it was reverted in the release branch. If the 3.0.x
release schedule does not allow waiting for this to complete, reverting it in
the release branch (i.e. branch-3.0.3) is an option.
> 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
