Return-Path: X-Original-To: apmail-hadoop-yarn-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 491B318B28 for ; Thu, 12 Nov 2015 13:26:44 +0000 (UTC) Received: (qmail 63434 invoked by uid 500); 12 Nov 2015 13:26:43 -0000 Delivered-To: apmail-hadoop-yarn-dev-archive@hadoop.apache.org Received: (qmail 60926 invoked by uid 500); 12 Nov 2015 13:26:39 -0000 Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-dev@hadoop.apache.org Delivered-To: mailing list yarn-dev@hadoop.apache.org Received: (qmail 59913 invoked by uid 99); 12 Nov 2015 13:26:38 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Nov 2015 13:26:38 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 83A531A218F; Thu, 12 Nov 2015 13:26:36 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.881 X-Spam-Level: ** X-Spam-Status: No, score=2.881 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 3Yke75K5O-1o; Thu, 12 Nov 2015 13:26:30 +0000 (UTC) Received: from mail-yk0-f178.google.com (mail-yk0-f178.google.com [209.85.160.178]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id CEE9C429A6; Thu, 12 Nov 2015 13:26:29 +0000 (UTC) Received: by ykba77 with SMTP id a77so93769686ykb.2; Thu, 12 Nov 2015 05:26:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type; bh=H6VyUQforcISM5mCt+drIzqTFWJY6yHIvNL6UAV2EXw=; b=nOme5BdaGOJmORtic3qAcvwv/dWzOGqxd5j1/hPtvXs+EMJbgNejuHCNqmwROV1R0J ENHvrtUjYEyJLmknXiD5ncmq1Qt/lOseN7NdnpP4M+IWBUlT/Chv4d8HagiiGS/EMkCk y16UYhD/BcTiS2wW8hIZqtC3qliZsIgO9GJreg25O/jnkGwujNMheOkRSuM5VWYugoSi ejiGn4NlcfEjUSTrRpqcA4Lxg5bGOfv9TzMfVMJjg0uJvHfKiH7qpGfsHoN95al/yAn1 0vtrgzowHtkaCweg1Sj+twInBwKcFOlS1JIj1+InkZhMqr4NA+0KnuigaU9bRztjTrzV Fbpg== X-Received: by 10.129.128.65 with SMTP id q62mr16288344ywf.210.1447334789285; Thu, 12 Nov 2015 05:26:29 -0800 (PST) MIME-Version: 1.0 References: <0C22896E-D77B-4DE4-99A2-9D81E150779C@hortonworks.com> <3505A424-5B02-49FA-9B56-AF13D20FEABD@altiscale.com> In-Reply-To: From: Sunil Govind Date: Thu, 12 Nov 2015 13:26:20 +0000 Message-ID: Subject: Re: [DISCUSS] Looking to a 2.8.0 release To: common-dev@hadoop.apache.org, "yarn-dev@hadoop.apache.org" Cc: "hdfs-dev@hadoop.apache.org" , "mapreduce-dev@hadoop.apache.org" , "vinodkv@apache.org" Content-Type: multipart/alternative; boundary=94eb2c030e18fc901c052457e349 --94eb2c030e18fc901c052457e349 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Thank you Vinod for starting this discussion. +1 for getting a beta/alpha version for Application Priority (YARN-1963). Major patches are already in and MAPREDUCE-5870 (making MR also to use app-priority) is in final review stages. This feature is also tested in-house. With 2.8.0 alpha, I feel we can see more use case based testing on same. A documentation JIRA is already raised for App Priority, and I will mark it for 2.8 so that it will be done before the RC cut. Thank You Sunil On Thu, Nov 12, 2015 at 2:41 AM Vinod Vavilapalli wrote: > I=E2=80=99ll let others comment on specific features. > > Regarding the 3.x vs 2.x point, as I noted before on other threads, given > all the incompatibilities in trunk it will be ways off before users can r= un > their production workloads on a 3.x release. Therefore, as I was proposin= g > before, we should continue the 2.x lines, but soon get started on rolling > out a release candidate based off trunk. > > Like with 2.8, I=E2=80=99d like to go back and prepare some notes on trun= k=E2=80=99s > content so we can objectively discuss about it. > > +Vinod --94eb2c030e18fc901c052457e349--