Return-Path: X-Original-To: apmail-hadoop-common-dev-archive@www.apache.org Delivered-To: apmail-hadoop-common-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 61AEC101D7 for ; Fri, 6 Dec 2013 21:54:35 +0000 (UTC) Received: (qmail 49490 invoked by uid 500); 6 Dec 2013 21:54:32 -0000 Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org Received: (qmail 49270 invoked by uid 500); 6 Dec 2013 21:54:32 -0000 Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-dev@hadoop.apache.org Delivered-To: mailing list common-dev@hadoop.apache.org Received: (qmail 49253 invoked by uid 99); 6 Dec 2013 21:54:32 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Dec 2013 21:54:32 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of acm@hortonworks.com designates 209.85.160.54 as permitted sender) Received: from [209.85.160.54] (HELO mail-pb0-f54.google.com) (209.85.160.54) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Dec 2013 21:54:27 +0000 Received: by mail-pb0-f54.google.com with SMTP id un15so1826536pbc.27 for ; Fri, 06 Dec 2013 13:54:07 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:mime-version:subject:date :references:to:in-reply-to:content-type; bh=cZTk5NOB54X69kUODMu7bF9R2NDSdxf47QuwVxrC668=; b=bS8sZUVujsvWvqAKdMt/JWPgfEet8zRHyGVYAOAgQwTr9tkdLoRZWxj2ruZhX+ubb2 D+5jFFt/NNTwoX20woE5CCw5Ao85vbhCHLPrPnG0XKnFFOq14qZqgh4o+3D/klJ/nhdb x2nVK58sGossaufnCLYfFwOMuRu1GD5T+0h5e7ock/GRekI6sDDC5Hmv/+yLWQesDoVX bCUpFziGb0khQ1DHOwIAG/1TFSIeCE5vSg7em5fGedie8Dv82JyxiOulW6alxX7uJeNG tmVjfzKhE1i+aD1HFA0YR+wn952Fzualoc/hJvJCT3mqC1AQK3oMtPen23ZmuddJuwY6 a+hA== X-Gm-Message-State: ALoCoQlaz8woUQbyNPTotcCjuYzEAH+3tXIdyxW3zEnFP9mm3OZGKic44H7iqIcx1NiIwYvqX7MutKfA3gQ4XnQLDeV8jhucGaeIv2NzR0ex/LwyaTakz+c= X-Received: by 10.68.190.103 with SMTP id gp7mr6711047pbc.74.1386366847534; Fri, 06 Dec 2013 13:54:07 -0800 (PST) Received: from [10.11.3.119] ([192.175.27.2]) by mx.google.com with ESMTPSA id ql10sm6073417pbc.44.2013.12.06.13.54.05 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 06 Dec 2013 13:54:06 -0800 (PST) From: Arun C Murthy Message-Id: Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: Next releases Date: Fri, 6 Dec 2013 13:53:59 -0800 References:

To: yarn-dev@hadoop.apache.org, "hdfs-dev@hadoop.apache.org" , "common-dev@hadoop.apache.org" , "mapreduce-dev@hadoop.apache.org" In-Reply-To: X-Mailer: Apple Mail (2.1510) Content-Type: multipart/alternative; boundary="Apple-Mail=_BFEB5DD2-7CF8-4553-A5A0-26A04D84F19C" X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_BFEB5DD2-7CF8-4553-A5A0-26A04D84F19C Content-Type: text/plain; charset=ISO-8859-1 Thanks Suresh & Colin. Please update the Roadmap wiki with your proposals. As always, we will try our best to get these in - but we can collectively decide to slip some of these to subsequent releases based on timelines. Arun On Dec 6, 2013, at 10:43 AM, Suresh Srinivas wrote: > Arun, > > I propose the following changes for 2.3: > - There have been a lot of improvements related to supporting http policy. > - There is a still discussion going on, but I would like to deprecate > BackupNode in 2.3 as well. > - We are currently working on rolling upgrades related change in HDFS. We > might add a couple of changes that enables rolling upgrades from 2.3 > onwards (hopefully we can this done by December) > > I propose the following for 2.4 release, if they are tested and stable: > - Heterogeneous storage support - HDFS-2832 > - Datanode cache related change - HDFS-4949 > - HDFS ACLs - HDFS-4685 > - Rolling upgrade changes > > Let me know if you want me to update the wiki. > > Regards, > Suresh > On Dec 6, 2013, at 12:27 PM, Colin McCabe wrote: > If 2.4 is released in January, I think it's very unlikely to include > symlinks. There is still a lot of work to be done before they're > usable. You can look at the progress on HADOOP-10019. For some of > the subtasks, it will require some community discussion before any > code can be written. > > For better or worse, symlinks have not been requested by users as > often as features like NFS export, HDFS caching, ACLs, etc, so effort > has been focused on those instead. > > For now, I think we should put the symlinks-disabling patches > (HADOOP-10020, etc) into branch-2, so that they will be part of the > next releases without additional effort. > > I would like to see HDFS caching make it into 2.4. The APIs and > implementation are beginning to stabilize, and around January it > should be ok to backport to a stable branch. > > best, > Colin > > > On Thu, Nov 7, 2013 at 6:42 PM, Arun C Murthy wrote: > >> Gang, >> >> Thinking through the next couple of releases here, appreciate f/b. >> >> # hadoop-2.2.1 >> >> I was looking through commit logs and there is a *lot* of content here >> (81 commits as on 11/7). Some are features/improvements and some are fixes >> - it's really hard to distinguish what is important and what isn't. >> >> I propose we start with a blank slate (i.e. blow away branch-2.2 and >> start fresh from a copy of branch-2.2.0) and then be very careful and >> meticulous about including only *blocker* fixes in branch-2.2. So, most of >> the content here comes via the next minor release (i.e. hadoop-2.3) >> >> In future, we continue to be *very* parsimonious about what gets into a >> patch release (major.minor.patch) - in general, these should be only >> *blocker* fixes or key operational issues. >> >> # hadoop-2.3 >> >> I'd like to propose the following features for YARN/MR to make it into >> hadoop-2.3 and punt the rest to hadoop-2.4 and beyond: >> * Application History Server - This is happening in a branch and is >> close; with it we can provide a reasonable experience for new frameworks >> being built on top of YARN. >> * Bug-fixes in RM Restart >> * Minimal support for long-running applications (e.g. security) via >> YARN-896 >> * RM Fail-over via ZKFC >> * Anything else? >> >> HDFS??? >> >> Overall, I feel like we have a decent chance of rolling hadoop-2.3 by the >> end of the year. >> >> Thoughts? >> >> thanks, >> Arun >> >> >> -- >> Arun C. Murthy >> Hortonworks Inc. >> http://hortonworks.com/ >> >> >> >> -- >> CONFIDENTIALITY NOTICE >> NOTICE: This message is intended for the use of the individual or entity to >> which it is addressed and may contain information that is confidential, >> privileged and exempt from disclosure under applicable law. If the reader >> of this message is not the intended recipient, you are hereby notified that >> any printing, copying, dissemination, distribution, disclosure or >> forwarding of this communication is strictly prohibited. If you have >> received this communication in error, please contact the sender immediately >> and delete it from your system. Thank You. >> > > > > -- > http://hortonworks.com/download/ > > -- > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity to > which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You. -- Arun C. Murthy Hortonworks Inc. http://hortonworks.com/ -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. --Apple-Mail=_BFEB5DD2-7CF8-4553-A5A0-26A04D84F19C--