hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4493) move queue can make app don't belong to any queue
Date Wed, 10 Feb 2016 04:54:18 GMT

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

Karthik Kambatla commented on YARN-4493:
----------------------------------------

[~jiangyu1211] - thanks for reporting this and posting a patch. Mind adding a unit test? 

> move queue can make app don't belong to any queue
> -------------------------------------------------
>
>                 Key: YARN-4493
>                 URL: https://issues.apache.org/jira/browse/YARN-4493
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: fairscheduler
>    Affects Versions: 2.4.0, 2.6.0, 2.7.1
>            Reporter: jiangyu
>            Priority: Minor
>         Attachments: yarn-4493.patch.1
>
>
> When moving a running application to a different queue, the current implement don't check
if the app can run in the new queue before remove it from current queue. So if the destination
queue is full, the app will throw exception, and don't belong to any queue.    
> After that, the queue become orphane, can not schedule any resources. If you kill the
app,  the removeApp method in FSLeafQueue will throw IllealStateException of "Given app to
remove app does not exist in queue ..." exception.   
> So i think we should check if the destination queue can run the app before remove it
from the current queue.  
> The patch is from our revision.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message