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 02F74176DB for ; Fri, 22 Jan 2016 06:50:40 +0000 (UTC) Received: (qmail 70381 invoked by uid 500); 22 Jan 2016 06:50:40 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 70304 invoked by uid 500); 22 Jan 2016 06:50:40 -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 70009 invoked by uid 99); 22 Jan 2016 06:50:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Jan 2016 06:50:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id E77FB2C1F64 for ; Fri, 22 Jan 2016 06:50:39 +0000 (UTC) Date: Fri, 22 Jan 2016 06:50:39 +0000 (UTC) From: "Weiwei Yang (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-4621) Job failed if time on one NM is out of sync even other nodes are sync'd 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-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiwei Yang updated YARN-4621: ------------------------------ Description: RM tried allocated more than 10 containers on a NM (on which time is out of sync), they all failed with token expired error, and job eventually failed. We can add a new state to NodeState, e.g DESYNC, if a node is not sync'd with RM, RM then can skip allocating containers on this node. was: RM tried allocated more than 10 containers on a NM (on which time is out of sync), they all failed with token expired error, and job eventually failed. We can add a new state to NodeState, e.g UNSYNC, if a node is not sync'd with RM, RM then can skip allocating containers on this node. > Job failed if time on one NM is out of sync even other nodes are sync'd > ----------------------------------------------------------------------- > > Key: YARN-4621 > URL: https://issues.apache.org/jira/browse/YARN-4621 > Project: Hadoop YARN > Issue Type: Improvement > Components: nodemanager, resourcemanager > Reporter: Weiwei Yang > Assignee: Weiwei Yang > Attachments: terasort_job_failed.log > > > RM tried allocated more than 10 containers on a NM (on which time is out of sync), they all failed with token expired error, and job eventually failed. We can add a new state to NodeState, e.g DESYNC, if a node is not sync'd with RM, RM then can skip allocating containers on this node. -- This message was sent by Atlassian JIRA (v6.3.4#6332)