[
https://issues.apache.org/jira/browse/YARN-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735676#comment-14735676
]
MENG DING commented on YARN-1651:
---------------------------------
Hi, [~leftnoteasy]
bq. I agree the general idea, and we should do the similar thing. However, I'm
not sure caching in RM is a good idea, potentially a malicious AM can send
millions of unknown-to-be-decreased-containers to RM when RM started. Maybe
it's better to cache in AMRMClient side. I think we can do this in a separated
JIRA? Could you file a new JIRA for this if you agree?
Your proposal makes sense. I will file a JIRA for this.
Thanks for addressing my comments. I don't have more comments for now. As per
our discussion, I will come up with an end-to-end test based on
distributedshell, and post onto this JIRA for review.
> CapacityScheduler side changes to support increase/decrease container
> resource.
> -------------------------------------------------------------------------------
>
> Key: YARN-1651
> URL: https://issues.apache.org/jira/browse/YARN-1651
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager, scheduler
> Reporter: Wangda Tan
> Assignee: Wangda Tan
> Attachments: YARN-1651-1.YARN-1197.patch,
> YARN-1651-2.YARN-1197.patch, YARN-1651-3.YARN-1197.patch,
> YARN-1651-4.YARN-1197.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
