hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiao Chen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-15450) Avoid fsync storm triggered by DiskChecker and handle disk full situation
Date Thu, 24 May 2018 18:51:00 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-15450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16489583#comment-16489583

Xiao Chen commented on HADOOP-15450:

Thanks all for the work here.

As [~gabor.bota] found out in an offline review, it seems the whitespace and checkstyle are
not addressed before committing. I understand everyone is busy, but this is a bad practice
and should not be followed. :)

> 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 For: 3.1.0, 2.10.0, 3.2.0, 3.1.1, 2.9.2, 2.8.5
>         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

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

View raw message