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/02/15 02:08:42 UTC
[jira] [Commented] (YARN-6180) Clean unused SchedulerRequestKeys
once ExecutionType updates are completed
[ https://issues.apache.org/jira/browse/YARN-6180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15867100#comment-15867100 ]
Subru Krishnan commented on YARN-6180:
--------------------------------------
[~asuresh], IIUC this is valid for all key attributes and not just ExecutionType updates?
> Clean unused SchedulerRequestKeys once ExecutionType updates are completed
> --------------------------------------------------------------------------
>
> Key: YARN-6180
> URL: https://issues.apache.org/jira/browse/YARN-6180
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Arun Suresh
> Assignee: Arun Suresh
>
> The SchedulerRequestKeys used for ExecutionType updates, that are generated, tend to accumulate in the AppSchedulingInfo and over time lead to a situation outlined in YARN-5540.
> These keys must be removed once the container update completes.
--
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