hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Graves (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-460) CS user left in list of active users for the queue even when application finished
Date Fri, 29 Mar 2013 13:41:15 GMT

     [ https://issues.apache.org/jira/browse/YARN-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Thomas Graves updated YARN-460:

    Attachment: YARN-460.patch

trunk patch.  After thinking about this more and talking to Arun a bit about it. I have made
this patch just contain the check for stopped and it returns an EMPTY_ALLOCATION similar to
what it did before if the application was null when calling allocate().  I will file a follow
up jira to investigate if the AMResponse should have another field so that the RM could send
the AM useful error information other then just reboot.
> CS user left in list of active users for the queue even when application finished
> ---------------------------------------------------------------------------------
>                 Key: YARN-460
>                 URL: https://issues.apache.org/jira/browse/YARN-460
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacityscheduler
>    Affects Versions: 0.23.7, 2.0.4-alpha
>            Reporter: Thomas Graves
>            Assignee: Thomas Graves
>            Priority: Blocker
>         Attachments: YARN-460-branch-0.23.patch, YARN-460-branch-0.23.patch, YARN-460-branch-0.23.patch,
YARN-460.patch, YARN-460.patch, YARN-460.patch, YARN-460.patch
> We have seen a user get left in the queues list of active users even though the application
was removed. This can cause everyone else in the queue to get less resources if using the
minimum user limit percent config.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message