hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3265) CapacityScheduler deadlock when computing absolute max avail capacity (fix for trunk/branch-2)
Date Mon, 02 Mar 2015 21:34:05 GMT

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

Vinod Kumar Vavilapalli commented on YARN-3265:
-----------------------------------------------

Looks good, +1. Will commit it if/when Jenkins says okay.

> CapacityScheduler deadlock when computing absolute max avail capacity (fix for trunk/branch-2)
> ----------------------------------------------------------------------------------------------
>
>                 Key: YARN-3265
>                 URL: https://issues.apache.org/jira/browse/YARN-3265
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacityscheduler, resourcemanager
>            Reporter: Wangda Tan
>            Assignee: Wangda Tan
>            Priority: Blocker
>         Attachments: YARN-3265.1.patch, YARN-3265.2.patch, YARN-3265.3.patch, YARN-3265.5.patch,
YARN-3265.6.patch, YARN-3265.7.patch
>
>
> This patch is trying to solve the same problem described in YARN-3251, but this is a
longer term fix for trunk and branch-2.



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

Mime
View raw message