Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 934DE11DDE for ; Sat, 23 Aug 2014 02:54:12 +0000 (UTC) Received: (qmail 85873 invoked by uid 500); 23 Aug 2014 02:54:12 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 85787 invoked by uid 500); 23 Aug 2014 02:54:12 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 85412 invoked by uid 99); 23 Aug 2014 02:54:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 23 Aug 2014 02:54:12 +0000 Date: Sat, 23 Aug 2014 02:54:12 +0000 (UTC) From: "Hadoop QA (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-1458) In Fair Scheduler, size based weight can cause update thread to hold lock indefinitely MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-1458?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D14107= 822#comment-14107822 ]=20 Hadoop QA commented on YARN-1458: --------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest a= ttachment=20 http://issues.apache.org/jira/secure/attachment/12663814/YARN-1458.004.pa= tch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author= tags. {color:green}+1 tests included{color}. The patch appears to include 2 = new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the = total number of javac compiler warnings. {color:green}+1 javadoc{color}. There were no new javadoc warning mess= ages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:e= clipse. {color:green}+1 findbugs{color}. The patch does not introduce any new = Findbugs (version 2.0.3) warnings. {color:green}+1 release audit{color}. The applied patch does not incre= ase the total number of release audit warnings. {color:red}-1 core tests{color}. The patch failed these unit tests in = hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resou= rcemanager: org.apache.hadoop.yarn.server.resourcemanager.application= smanager.TestAMRestart {color:green}+1 contrib tests{color}. The patch passed contrib unit te= sts. Test results: https://builds.apache.org/job/PreCommit-YARN-Build/4702//test= Report/ Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4702//co= nsole This message is automatically generated. > In Fair Scheduler, size based weight can cause update thread to hold lock= indefinitely > -------------------------------------------------------------------------= ------------- > > Key: YARN-1458 > URL: https://issues.apache.org/jira/browse/YARN-1458 > Project: Hadoop YARN > Issue Type: Bug > Components: scheduler > Affects Versions: 2.2.0 > Environment: Centos 2.6.18-238.19.1.el5 X86_64 > hadoop2.2.0 > Reporter: qingwu.fu > Assignee: zhihai xu > Labels: patch > Fix For: 2.2.1 > > Attachments: YARN-1458.001.patch, YARN-1458.002.patch, YARN-1458.= 003.patch, YARN-1458.004.patch, YARN-1458.patch > > Original Estimate: 408h > Remaining Estimate: 408h > > The ResourceManager$SchedulerEventDispatcher$EventProcessor blocked when = clients submit lots jobs, it is not easy to reapear. We run the test cluste= r for days to reapear it. The output of jstack command on resourcemanager = pid: > {code} > "ResourceManager Event Processor" prio=3D10 tid=3D0x00002aaab0c5f000 nid= =3D0x5dd3 waiting for monitor entry [0x0000000043aa9000] > java.lang.Thread.State: BLOCKED (on object monitor) > at org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.F= airScheduler.removeApplication(FairScheduler.java:671) > - waiting to lock <0x000000070026b6e0> (a org.apache.hadoop.yarn.= server.resourcemanager.scheduler.fair.FairScheduler) > at org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.F= airScheduler.handle(FairScheduler.java:1023) > at org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.F= airScheduler.handle(FairScheduler.java:112) > at org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$= SchedulerEventDispatcher$EventProcessor.run(ResourceManager.java:440) > at java.lang.Thread.run(Thread.java:744) > =E2=80=A6=E2=80=A6 > "FairSchedulerUpdateThread" daemon prio=3D10 tid=3D0x00002aaab0a2c800 nid= =3D0x5dc8 runnable [0x00000000433a2000] > java.lang.Thread.State: RUNNABLE > at org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.F= airScheduler.getAppWeight(FairScheduler.java:545) > - locked <0x000000070026b6e0> (a org.apache.hadoop.yarn.server.re= sourcemanager.scheduler.fair.FairScheduler) > at org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.A= ppSchedulable.getWeights(AppSchedulable.java:129) > at org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.p= olicies.ComputeFairShares.computeShare(ComputeFairShares.java:143) > at org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.p= olicies.ComputeFairShares.resourceUsedWithWeightToResourceRatio(ComputeFair= Shares.java:131) > at org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.p= olicies.ComputeFairShares.computeShares(ComputeFairShares.java:102) > at org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.p= olicies.FairSharePolicy.computeShares(FairSharePolicy.java:119) > at org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.F= SLeafQueue.recomputeShares(FSLeafQueue.java:100) > at org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.F= SParentQueue.recomputeShares(FSParentQueue.java:62) > at org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.F= airScheduler.update(FairScheduler.java:282) > - locked <0x000000070026b6e0> (a org.apache.hadoop.yarn.server.re= sourcemanager.scheduler.fair.FairScheduler) > at org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.F= airScheduler$UpdateThread.run(FairScheduler.java:255) > at java.lang.Thread.run(Thread.java:744) > {code} -- This message was sent by Atlassian JIRA (v6.2#6252)