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 "Subru Krishnan (JIRA)" <ji...@apache.org> on 2017/05/01 22:03:04 UTC
[jira] [Updated] (YARN-6541) Optimize
PeriodicRLESparseResourceAllocation by auto-expanding it's time period
[ https://issues.apache.org/jira/browse/YARN-6541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Subru Krishnan updated YARN-6541:
---------------------------------
Summary: Optimize PeriodicRLESparseResourceAllocation by auto-expanding it's time period (was: Optimize {{PeriodicRLESparseResourceAllocation}} by auto-expanding it's time period)
> Optimize PeriodicRLESparseResourceAllocation by auto-expanding it's time period
> -------------------------------------------------------------------------------
>
> Key: YARN-6541
> URL: https://issues.apache.org/jira/browse/YARN-6541
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Subru Krishnan
>
> YARN-5531 adds a the specified {{PeriodicRLESparseResourceAllocation}} that represents periodic allocation of resources. It seeds the period directly using the max timePeriod which will result in storing multiple instances if the user requested periods are small. For e.g: 24 instances of an hourly job if timePeriod is one day. We need the max to prevent unbounded time period if user decides to input prime numbers but we can auto-expand instead of statically fixing it as the period
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org