hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3943) Use separate threshold configurations for disk-full detection and disk-not-full detection.
Date Thu, 08 Oct 2015 22:24:27 GMT

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

Jason Lowe commented on YARN-3943:
----------------------------------

+1 lgtm.  Committing this.

> Use separate threshold configurations for disk-full detection and disk-not-full detection.
> ------------------------------------------------------------------------------------------
>
>                 Key: YARN-3943
>                 URL: https://issues.apache.org/jira/browse/YARN-3943
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager
>            Reporter: zhihai xu
>            Assignee: zhihai xu
>            Priority: Critical
>         Attachments: YARN-3943.000.patch, YARN-3943.001.patch, YARN-3943.002.patch
>
>
> Use separate threshold configurations to check when disks become full and when disks
become good. Currently the configuration "yarn.nodemanager.disk-health-checker.max-disk-utilization-per-disk-percentage"
and "yarn.nodemanager.disk-health-checker.min-free-space-per-disk-mb" are used to check both
when disks become full and when disks become good. It will be better to use two configurations:
one is used when disks become full from not-full and the other one is used when disks become
not-full from full. So we can avoid oscillating frequently.
> For example: we can set the one for disk-full detection higher than the one for disk-not-full
detection.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message