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 0111D17F24 for ; Fri, 16 Oct 2015 16:46:07 +0000 (UTC) Received: (qmail 36055 invoked by uid 500); 16 Oct 2015 16:46:05 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 35996 invoked by uid 500); 16 Oct 2015 16:46:05 -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 35780 invoked by uid 99); 16 Oct 2015 16:46:05 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Oct 2015 16:46:05 +0000 Date: Fri, 16 Oct 2015 16:46:05 +0000 (UTC) From: "Junping Du (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-4274) NodeStatusUpdaterImpl should register to RM again after a non-fatal exception happen before 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-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-4274: ----------------------------- Description: From YARN-3896, an non-fatal exception like response ID mismatch between NM and RM (due to a race condition) will cause NM stop working. I think we should make it more robust to tolerant a few failure in registering to RM with retry a few times. (was: From YARN-3896, an non-fatal exception like response ID mismatch between NM and RM (due to a race condition) will cause NM stop working. I think we should make it more robust to tolerant a few times failure in registering to RM.) > NodeStatusUpdaterImpl should register to RM again after a non-fatal exception happen before > ------------------------------------------------------------------------------------------- > > Key: YARN-4274 > URL: https://issues.apache.org/jira/browse/YARN-4274 > Project: Hadoop YARN > Issue Type: Improvement > Reporter: Junping Du > Assignee: Junping Du > > From YARN-3896, an non-fatal exception like response ID mismatch between NM and RM (due to a race condition) will cause NM stop working. I think we should make it more robust to tolerant a few failure in registering to RM with retry a few times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)