Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D7D7C17B9E for ; Fri, 13 Mar 2015 00:07:27 +0000 (UTC) Received: (qmail 83748 invoked by uid 500); 13 Mar 2015 00:07:22 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 83417 invoked by uid 500); 13 Mar 2015 00:07:22 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 83393 invoked by uid 99); 13 Mar 2015 00:07:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Mar 2015 00:07:21 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of sumasai.shivaprasad@gmail.com designates 209.85.213.41 as permitted sender) Received: from [209.85.213.41] (HELO mail-yh0-f41.google.com) (209.85.213.41) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Mar 2015 00:07:16 +0000 Received: by yhaf73 with SMTP id f73so10065706yha.12; Thu, 12 Mar 2015 17:04:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=GQStZMA+CG6yxPyHhrJ5iJpZyBkuXfZ4vys/SkUd84s=; b=wP1CM+SOceLP4uXVIbldE93ZqG2fxJNzoJhFycjm6nCWlJ048RKyTfIxyDR2hjXFIc cDOe1uvgNXABD734sRarRwMsIiRpLQxSWAC95LmfmNCN6FloBsIFCm4k4m4K/sV7eHUV KW0BWoMgkiW56VUBWKrc9AakwXaVGPyxQpBA79xwnkH3/q9boQJQYeRb1G1ekXhWDTnN jPjPZhfBxHfvKLCC81TkC4aHLyKU+FU30J8tKsf6EEitqMJZeTbT8By7E3HIByyLKFdg 0WGFFBkHRevaGkjSw69gHGDAe15KKZg1f5l6fgFjWtk4CWXQSpLxKmbpq5ne8+A7QMUJ skCQ== MIME-Version: 1.0 X-Received: by 10.236.227.198 with SMTP id d66mr43436811yhq.147.1426205080323; Thu, 12 Mar 2015 17:04:40 -0700 (PDT) Received: by 10.170.126.141 with HTTP; Thu, 12 Mar 2015 17:04:40 -0700 (PDT) Date: Fri, 13 Mar 2015 05:34:40 +0530 Message-ID: Subject: Deadlock in RM From: Suma Shivaprasad To: "yarn-dev@hadoop.apache.org" , "user@hadoop.apache.org" Content-Type: multipart/alternative; boundary=001a11c2dbf8308d250511203fd3 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c2dbf8308d250511203fd3 Content-Type: text/plain; charset=UTF-8 We are observing a repetitive issue with hadoop 2.6.0/HDP 2.2 with RM capacity scheduler threads getting into a deadlock. It appears that the RM UI scheduler flow for getResourceUsageReport is triggering the deadlock. Have raised a jira for the same - *https://issues.apache.org/jira/browse/YARN-3346 *. Can someone please take a look and get back with your thoughts on this. Thanks Suma --001a11c2dbf8308d250511203fd3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
We are ob= serving a repetitive issue with hadoop 2.6.0/HDP 2.2 with RM capacity sched= uler threads getting into a deadlock. It appears that the RM UI scheduler f= low for getResourceUsageReport is triggering the deadlock.

Have raised a jira for the same -=C2=A0https://issues.ap= ache.org/jira/browse/YARN-3346. Can someone please take a look and = get back with your thoughts on this.

Thanks<= /div>
Suma
--001a11c2dbf8308d250511203fd3--