Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Sat, 21 Nov 2015 08:50:11 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12840583.1435248980000.147221.1448095811150@Atlassian.JIRA>
In-Reply-To: <JIRA.12840583.1435248980000@Atlassian.JIRA>
References: <JIRA.12840583.1435248980000@Atlassian.JIRA>
 <JIRA.12840583.1435248980415@arcas>
Subject: [jira] [Commented] (YARN-3849) Too much of preemption activity
 causing continuos killing of containers across queues
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/YARN-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15020334#comment-15020334 ] 

Hudson commented on YARN-3849:
------------------------------

FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #624 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/624/])
move YARN-4326/YARN-3849 from 2.8.0 to 2.7.3 (wangda: rev a30eccb38c83b20af5d0705f9834165b74468314)
* 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
>
>         Attachments: 0001-YARN-3849.patch, 0002-YARN-3849.patch, 0003-YARN-3849.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)