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 327EA18827 for ; Fri, 18 Sep 2015 17:15:12 +0000 (UTC) Received: (qmail 65820 invoked by uid 500); 18 Sep 2015 17:15:05 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 65775 invoked by uid 500); 18 Sep 2015 17:15: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 65764 invoked by uid 99); 18 Sep 2015 17:15:05 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Sep 2015 17:15:05 +0000 Date: Fri, 18 Sep 2015 17:15:05 +0000 (UTC) From: "Hudson (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-3212) RMNode State Transition Update with DECOMMISSIONING state MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-3212?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D14875= 969#comment-14875969 ]=20 Hudson commented on YARN-3212: ------------------------------ FAILURE: Integrated in Hadoop-trunk-Commit #8482 (See [https://builds.apach= e.org/job/Hadoop-trunk-Commit/8482/]) YARN-3212. RMNode State Transition Update with DECOMMISSIONING state. (Junp= ing Du via wangda) (wangda: rev 9bc913a35c46e65d373c3ae3f01a377e16e8d0ca) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-res= ourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rm= node/RMNodeImpl.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-res= ourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/Re= sourceTrackerService.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-res= ourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/we= bapp/TestNodesPage.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-res= ourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/Te= stRMNodeTransitions.java * hadoop-yarn-project/CHANGES.txt * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-res= ourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/No= desListManager.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-res= ourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rm= node/RMNodeEventType.java > RMNode State Transition Update with DECOMMISSIONING state > --------------------------------------------------------- > > Key: YARN-3212 > URL: https://issues.apache.org/jira/browse/YARN-3212 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager > Reporter: Junping Du > Assignee: Junping Du > Fix For: 2.8.0 > > Attachments: RMNodeImpl - new.png, YARN-3212-v1.patch, YARN-3212-= v2.patch, YARN-3212-v3.patch, YARN-3212-v4.1.patch, YARN-3212-v4.patch, YAR= N-3212-v5.1.patch, YARN-3212-v5.patch, YARN-3212-v6.1.patch, YARN-3212-v6.2= .patch, YARN-3212-v6.patch > > > As proposed in YARN-914, a new state of =E2=80=9CDECOMMISSIONING=E2=80=9D= will be added and can transition from =E2=80=9Crunning=E2=80=9D state trig= gered by a new event - =E2=80=9Cdecommissioning=E2=80=9D.=20 > This new state can be transit to state of =E2=80=9Cdecommissioned=E2=80= =9D when Resource_Update if no running apps on this NM or NM reconnect afte= r restart. Or it received DECOMMISSIONED event (after timeout from CLI). > In addition, it can back to =E2=80=9Crunning=E2=80=9D if user decides to = cancel previous decommission by calling recommission on the same node. The = reaction to other events is similar to RUNNING state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)