You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Sunil Govindan (JIRA)" <ji...@apache.org> on 2018/11/17 03:24:10 UTC
[jira] [Updated] (YARN-6723) NM overallocation based on over-time
rather than snapshot utilization
[ https://issues.apache.org/jira/browse/YARN-6723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sunil Govindan updated YARN-6723:
---------------------------------
Target Version/s: 3.3.0 (was: 3.2.0)
Bulk update: moved all 3.2.0 non-blocker issues, please move back if it is a blocker.
> NM overallocation based on over-time rather than snapshot utilization
> ---------------------------------------------------------------------
>
> Key: YARN-6723
> URL: https://issues.apache.org/jira/browse/YARN-6723
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: yarn
> Affects Versions: 3.0.0-alpha3
> Reporter: Haibo Chen
> Assignee: Haibo Chen
> Priority: Major
>
> To continue discussion on Miklos's idea in YARN-6670 of
> "Usually the CPU usage fluctuates quite a bit. Do not we need a time period for NM_OVERALLOCATION_GENERAL_THRESHOLD, etc. to avoid allocating on small glitches, even worse preempting in those cases?"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org