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 1939610064 for ; Thu, 11 Dec 2014 18:00:17 +0000 (UTC) Received: (qmail 91078 invoked by uid 500); 11 Dec 2014 18:00:16 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 90988 invoked by uid 500); 11 Dec 2014 18:00:16 -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 90750 invoked by uid 99); 11 Dec 2014 18:00:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Dec 2014 18:00:16 +0000 Date: Thu, 11 Dec 2014 18:00:16 +0000 (UTC) From: "Jian He (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-2917) Potential deadlock in AsyncDispatcher when system.exit called in AsyncDispatcher#dispatch and AsyscDispatcher#serviceStop from shutdown hook MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14242853#comment-14242853 ] Jian He commented on YARN-2917: ------------------------------- patch looks good, thanks Rohith ! Committing this. bq. I observed that ResourceManager#rmDispatcher does not drain ,is it bug? I think the decision was to make the state-store relevant dispatcher drained. rmDispatcher is a global dispatcher. draining that may take more time depending on how busy the cluster is. I think it's still fine to drain the rmDispatcher, but need to evaluate the pros and cons. > Potential deadlock in AsyncDispatcher when system.exit called in AsyncDispatcher#dispatch and AsyscDispatcher#serviceStop from shutdown hook > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: YARN-2917 > URL: https://issues.apache.org/jira/browse/YARN-2917 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager > Reporter: Rohith > Assignee: Rohith > Priority: Critical > Attachments: 0001-YARN-2917.patch, 0002-YARN-2917.patch > > > I encoutered scenario where RM hanged while shutting down and keep on logging {{2014-12-03 19:32:44,283 INFO org.apache.hadoop.yarn.event.AsyncDispatcher: Waiting for AsyncDispatcher to drain.}} -- This message was sent by Atlassian JIRA (v6.3.4#6332)