[
https://issues.apache.org/jira/browse/YARN-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15091522#comment-15091522
]
Hudson commented on YARN-3849:
------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #9080 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/9080/])
Add YARN-3849 to Release 2.6.4 entry in CHANGES.txt (rohithsharmaks: rev
76e72708511100dbfaba910e120892b87b87edee)
* hadoop-yarn-project/CHANGES.txt
> Too much of preemption activity causing continuos killing of containers
> across queues
> -------------------------------------------------------------------------------------
>
> Key: YARN-3849
> URL: https://issues.apache.org/jira/browse/YARN-3849
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacityscheduler
> Affects Versions: 2.7.0
> Reporter: Sunil G
> Assignee: Sunil G
> Priority: Critical
> Fix For: 2.8.0, 2.7.3, 2.6.4
>
> Attachments: 0001-YARN-3849.patch, 0002-YARN-3849.patch,
> 0003-YARN-3849.patch, 0004-YARN-3849-branch2-6.patch,
> 0004-YARN-3849-branch2-7.patch, 0004-YARN-3849.patch
>
>
> Two queues are used. Each queue has given a capacity of 0.5. Dominant
> Resource policy is used.
> 1. An app is submitted in QueueA which is consuming full cluster capacity
> 2. After submitting an app in QueueB, there are some demand and invoking
> preemption in QueueA
> 3. Instead of killing the excess of 0.5 guaranteed capacity, we observed that
> all containers other than AM is getting killed in QueueA
> 4. Now the app in QueueB is trying to take over cluster with the current free
> space. But there are some updated demand from the app in QueueA which lost
> its containers earlier, and preemption is kicked in QueueB now.
> Scenario in step 3 and 4 continuously happening in loop. Thus none of the
> apps are completing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
