You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Wangda Tan (JIRA)" <ji...@apache.org> on 2015/02/26 01:30:05 UTC

[jira] [Commented] (YARN-3251) CapacityScheduler deadlock when computing absolute max avail capacity (short term fix for 2.6.1)

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

Wangda Tan commented on YARN-3251:
----------------------------------

+1 for the suggestion, moved it out of YARN-3243, changed target version and also updated title.

> CapacityScheduler deadlock when computing absolute max avail capacity (short term fix for 2.6.1)
> ------------------------------------------------------------------------------------------------
>
>                 Key: YARN-3251
>                 URL: https://issues.apache.org/jira/browse/YARN-3251
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.6.0
>            Reporter: Jason Lowe
>            Assignee: Wangda Tan
>            Priority: Blocker
>         Attachments: YARN-3251.1.patch, YARN-3251.trunk.1.patch
>
>
> The ResourceManager can deadlock in the CapacityScheduler when computing the absolute max available capacity for user limits and headroom.



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