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 "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2015/09/02 20:30:46 UTC

[jira] [Updated] (YARN-3487) CapacityScheduler scheduler lock obtained unnecessarily when calling getQueue

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

Vinod Kumar Vavilapalli updated YARN-3487:
------------------------------------------
    Fix Version/s: 2.6.1

Pulled this into 2.6.1. Ran compilation before the push. Patch applied cleanly.

> CapacityScheduler scheduler lock obtained unnecessarily when calling getQueue
> -----------------------------------------------------------------------------
>
>                 Key: YARN-3487
>                 URL: https://issues.apache.org/jira/browse/YARN-3487
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacityscheduler
>    Affects Versions: 2.6.0
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>            Priority: Critical
>              Labels: 2.6.1-candidate
>             Fix For: 2.6.1, 2.7.1
>
>         Attachments: YARN-3487.001.patch, YARN-3487.002.patch, YARN-3487.003.patch
>
>
> Recently saw a significant slowdown of applications on a large cluster, and we noticed there were a large number of blocked threads on the RM.  Most of the blocked threads were waiting for the CapacityScheduler lock while calling getQueueInfo.



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