hadoop-common-issues mailing list archives

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

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

Ajay Kumar commented on HADOOP-15450:
-------------------------------------

[~arpitagarwal] thanks for submitting the patch. test failure in TestDiskChecker is related
as we have changed method signature in {{TestDiskChecker#checkDisks}}. +1 with that addressed.

> 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
>
>
> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message