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 BCE0E1806F for ; Thu, 3 Mar 2016 19:17:19 +0000 (UTC) Received: (qmail 95039 invoked by uid 500); 3 Mar 2016 19:17:18 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 94967 invoked by uid 500); 3 Mar 2016 19:17:18 -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 94458 invoked by uid 99); 3 Mar 2016 19:17:18 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Mar 2016 19:17:18 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 38E9B2C1F6A for ; Thu, 3 Mar 2016 19:17:18 +0000 (UTC) Date: Thu, 3 Mar 2016 19:17:18 +0000 (UTC) From: "Eric Badger (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-4756) Unnecessary wait in Node Status Updater during reboot 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-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-4756: ------------------------------ Description: The startStatusUpdater thread waits for the isStopped variable to be set to true, but it is waiting for the next heartbeat. During a reboot, the next heartbeat will not come and so the thread waits for a timeout. Instead, we should notify the thread to continue so that it can check the isStopped variable and exit without having to wait for a timeout. (was: The Node Status Updater thread waits for the isStopped variable to be set to true, but it is waiting for the next heartbeat. During a reboot, the next heartbeat will not come and so the thread waits for a timeout. Instead, we should notify the thread to continue so that it can check the isStopped variable and exit without having to wait for a timeout. ) > Unnecessary wait in Node Status Updater during reboot > ----------------------------------------------------- > > Key: YARN-4756 > URL: https://issues.apache.org/jira/browse/YARN-4756 > Project: Hadoop YARN > Issue Type: Improvement > Reporter: Eric Badger > Assignee: Eric Badger > Attachments: YARN-4756.001.patch > > > The startStatusUpdater thread waits for the isStopped variable to be set to true, but it is waiting for the next heartbeat. During a reboot, the next heartbeat will not come and so the thread waits for a timeout. Instead, we should notify the thread to continue so that it can check the isStopped variable and exit without having to wait for a timeout. -- This message was sent by Atlassian JIRA (v6.3.4#6332)