[
https://issues.apache.org/jira/browse/YARN-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13967685#comment-13967685
]
Chris Douglas commented on YARN-1927:
-------------------------------------
The decision to preempt a container may be reversed. The policy reiterates its
request and only kills containers consistently recalled over a grace period.
The application clears the containers requested in
{{FiCaSchedulerApp::getAllocation}} after reporting them to the AM.
[~curino], can you confirm that this is the intent?
> Preemption message shouldn’t be created multiple times for same container-id
> in ProportionalCapacityPreemptionPolicy
> --------------------------------------------------------------------------------------------------------------------
>
> Key: YARN-1927
> URL: https://issues.apache.org/jira/browse/YARN-1927
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacityscheduler
> Affects Versions: 2.4.0
> Reporter: Wangda Tan
> Assignee: Wangda Tan
> Priority: Minor
> Attachments: YARN-1927.patch
>
>
> Currently, after each editSchedule() called, preemption message will be
> created and sent to scheduler. ProportionalCapacityPreemptionPolicy should
> only send preemption message once for each container.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
