Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 324D4200CFC for ; Thu, 28 Sep 2017 19:03:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 30E0E1609EE; Thu, 28 Sep 2017 17:03:08 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 783351609B4 for ; Thu, 28 Sep 2017 19:03:07 +0200 (CEST) Received: (qmail 8706 invoked by uid 500); 28 Sep 2017 17:03:03 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 8647 invoked by uid 99); 28 Sep 2017 17:03:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Sep 2017 17:03:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 6C6EFD256E for ; Thu, 28 Sep 2017 17:03:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id I7ZJCrIgr6-f for ; Thu, 28 Sep 2017 17:03:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 290EE61053 for ; Thu, 28 Sep 2017 17:03:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 72884E0EB1 for ; Thu, 28 Sep 2017 17:03:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id E6E69242BF for ; Thu, 28 Sep 2017 17:03:00 +0000 (UTC) Date: Thu, 28 Sep 2017 17:03:00 +0000 (UTC) From: "Arun Suresh (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-7248) NM returns new SCHEDULED container status to older clients MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 28 Sep 2017 17:03:08 -0000 [ https://issues.apache.org/jira/browse/YARN-7248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16184465#comment-16184465 ] Arun Suresh commented on YARN-7248: ----------------------------------- I don't mind creating a branch-3.0 patch, but unfortunately, this will not cleanly apply to branch-3.0 without first getting in YARN-5292 (YARN-5216 and YARN-6059 might also be required) and YARN-7240. I was waiting for Andrew to get beta1 out before pushing those in. > NM returns new SCHEDULED container status to older clients > ---------------------------------------------------------- > > Key: YARN-7248 > URL: https://issues.apache.org/jira/browse/YARN-7248 > Project: Hadoop YARN > Issue Type: Bug > Components: nodemanager > Affects Versions: 2.9.0, 3.0.0-alpha2 > Reporter: Jason Lowe > Assignee: Arun Suresh > Priority: Blocker > Attachments: YARN-7248.001.patch, YARN-7248.002.patch, YARN-7248.003.patch > > > YARN-4597 added a new SCHEDULED container state and that state is returned to clients when the container is localizing, etc. However the client may be running on an older software version that does not have the new SCHEDULED state which could lead the client to crash on the unexpected container state value or make incorrect assumptions like any state != NEW and != RUNNING must be COMPLETED which was true in the older version. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org