Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-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 D52EF18DD0 for ; Wed, 29 Jul 2015 07:38:52 +0000 (UTC) Received: (qmail 27894 invoked by uid 500); 29 Jul 2015 07:38:37 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 27601 invoked by uid 500); 29 Jul 2015 07:38:37 -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 27581 invoked by uid 99); 29 Jul 2015 07:38:37 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Jul 2015 07:38:37 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id D93731930E1; Wed, 29 Jul 2015 07:38:36 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.041 X-Spam-Level: ** X-Spam-Status: No, score=2.041 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H2=-1.108, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id n9HLkqwALVBw; Wed, 29 Jul 2015 07:38:36 +0000 (UTC) Received: from mail-io0-f181.google.com (mail-io0-f181.google.com [209.85.223.181]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id E018B428F6; Wed, 29 Jul 2015 07:38:35 +0000 (UTC) Received: by ioeg141 with SMTP id g141so12965701ioe.3; Wed, 29 Jul 2015 00:37:50 -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=y5MFGEnvz/8uggLQw4B6mNEYLtja6ZrBqZIrCsy8uGA=; b=fyg6Aq/i0+u+yzZY4TlEhi7qMKYejFOrxhljUGFUI51NhUJ/AMQLzgBD5SVf+1zo2N BnpWd8jWWWjKilXiQWf1da7f4f8tqGpxYo8kPK8oa1NCYTYFELEjOcNTJ9xhXD8TmUQW bPscOAK3cEkKkc0v54X/dtgwUj6eLaQhG7vvtHrkLDLLyheAJN8mEA5w7Arc1m80qGpC DDknq2QMkdf8Hccb9i/TF4mg7B0yHbJ3Abhd+ymMl0iqOMr/N2FxYML71T0cuAIPQVXG eRMAbZjXW9ACwe+AuVlp6WX2goMp1VuK6AcC0v/4ZxyTahgpjCv8ZQblVE8abE94Unl6 Ghrw== MIME-Version: 1.0 X-Received: by 10.107.12.82 with SMTP id w79mr64750109ioi.171.1438155470540; Wed, 29 Jul 2015 00:37:50 -0700 (PDT) Received: by 10.79.96.197 with HTTP; Wed, 29 Jul 2015 00:37:50 -0700 (PDT) Date: Wed, 29 Jul 2015 15:37:50 +0800 Message-ID: Subject: fair scheduler deadlock at FairSchedulerUpdateThread From: Jiacai Liu To: user@hadoop.apache.org, yarn-dev@hadoop.apache.org Content-Type: multipart/alternative; boundary=001a113dfe36f41aa4051bfea9fd --001a113dfe36f41aa4051bfea9fd Content-Type: text/plain; charset=UTF-8 I current use hadoop2.6.0 configured with fair scheduler. After trying Hive on Tez, it seems that fair scheduler get deadlock. The output of jstack, jmap and resourcemanager log is here: https://drive.google.com/file/d/0B7zV3Ct1fa9dQWJvZW9hR0Q0dHc/view And deadlock occurred at 2015-07-27 16:10, so you guys can focus at this time when read resourcemanager log. >From jstack, it seemed hung at FairSchedulerUpdateThread Hope above information can help debug this issue. Below link is original posted at tez user email list. http://mail-archives.apache.org/mod_mbox/tez-user/201507.mbox/%3C2343C6D2-FD65-43B9-AE72-9E77E0A0E7CD%40apache.org%3E Thanks --001a113dfe36f41aa4051bfea9fd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I current use= hadoop2.6.0 configured with=C2=A0fair scheduler.
After trying Hive on Tez, it seems that fair=C2=A0= scheduler get deadlock.
The output of jstack, j= map and resourcemanager log is here:

And deadlock= occurred at=C2=A02015-07-27 16:10, so you guys can focus at this time when= read resourcemanager log.

From jstack, it seem= ed =C2=A0hung at=C2=A0FairSchedulerUpdateThread

Hope above information can help debug this issue.


Below link is ori= ginal posted at tez user email list.

Thanks
--001a113dfe36f41aa4051bfea9fd--