Return-Path: X-Original-To: apmail-incubator-bigtop-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-bigtop-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 83993C5EE for ; Fri, 13 Jul 2012 16:56:01 +0000 (UTC) Received: (qmail 75285 invoked by uid 500); 13 Jul 2012 16:56:01 -0000 Delivered-To: apmail-incubator-bigtop-dev-archive@incubator.apache.org Received: (qmail 75220 invoked by uid 500); 13 Jul 2012 16:56:00 -0000 Mailing-List: contact bigtop-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: bigtop-dev@incubator.apache.org Delivered-To: mailing list bigtop-dev@incubator.apache.org Delivered-To: moderator for bigtop-dev@incubator.apache.org Received: (qmail 2707 invoked by uid 99); 12 Jul 2012 21:45:52 -0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL,URIBL_DBL_REDIR X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=uMCd+E3DU8GbjHnOPmODIFG895Em6OYFNidi+yHYKOY=; b=DjOC1Ib/bs4p5IzOgXGjGiM3VBhLk2anJWBGh9xm+GEdtKANmSC4pvSEKg3duyZvld YlWdjaABWf9QBhQuO/WaGFJAN1j9vUb0IGpf6qy8Ova6VwG9jQ7axHAju0YLNJtab71d p2FzSaAtxRJGaiNy+PtcLOM7Ixn3K/3EeFRMcvSEdV/0wAMRPMbAfEX0dIUSGIQnvEbW S9yTRS7ZxxluPHMFhxzgks/QWAbpBvceL5ZbYR/RKPr+CP5awRMH/nkY09KrDAS5iErj e12vYakTWAuqFPOAwXPQCNgAyngeJUkfDgIF0SZhubKSfYSizgLTYz6y98eT5I7p7zH+ XoYA== MIME-Version: 1.0 In-Reply-To: References: Date: Thu, 12 Jul 2012 14:45:25 -0700 Message-ID: Subject: Re: update re: Hadoop-1.1.0-rc0 From: Suresh Srinivas To: common-dev@hadoop.apache.org, mattf@apache.org Cc: bigtop-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=20cf307f343ea381fc04c4a8e138 X-Gm-Message-State: ALoCoQlSs84UNH8OA1q3SIYhFRCPjEUnW2i55IvrzXMmtKaBF0N4JEsh3TKy/P3P7zShN71dmxgi X-Virus-Checked: Checked by ClamAV on apache.org --20cf307f343ea381fc04c4a8e138 Content-Type: text/plain; charset=ISO-8859-1 Matt, Meanwhile, I am planning to promote the following changes: HDFS-2465 - Add HDFS support for fadvise readahead and drop-behind HADOOP-Support fadvise and sync_data_range in NativeIO, add ReadaheadPool class These changes should be low risk - These i/o improvements are turned off by default in configuration. Brandon Li has done quite a bit of testing (TestDFSIO, teragen, terasort, teravalidate etc.) on a small cluster (3 nodes) in addition to unit tests. Regards, Suresh On Thu, Jul 12, 2012 at 2:26 PM, Matt Foley wrote: > The following additional patches are committed to branch-1.1 and will be in > 1.1.0: > - HADOOP-8365 - Add flag to disable durable sync > - HADOOP-8399 - Remove JDK5 dependency from Hadoop 1.0+ line > - HADOOP-8417 - HADOOP-6963 didn't update hadoop-core-pom-template.xml > - HADOOP-8445 - Token should not print the password in toString > - MAPREDUCE-2903 - Map Tasks graph is throwing XML Parse error when Job is > executed with 0 maps > - MAPREDUCE-2129 - Job may hang if > mapreduce.job.committer.setup.cleanup.needed=false and > mapreduce.map/reduce.failures.maxpercent>0 > > I've been trying to build and test the RC0, but am having build problems > with the 32-bit version. Should have it figured out soon. > > The following patch is committed to branch-1 and I'll see if I can apply it > to branch-1.1 before my next build: > - HDFS-3617 - Port HDFS-96 to branch-1 (support blocks greater than 2GB) > > The following patch is committed to branch-1 but had conflicts with > branch-1.1 and will not be in RC0: > - HDFS-3596 - Improve FSEditLog pre-allocation in branch-1 > > The following patches are deferred, as they do not have currently committed > patches: > - HADOOP-7823 - port HADOOP-4012 to branch-1 (splitting support for bzip2) > - MAPREDUCE-4049 - plugin for generic shuffle service > > Thanks, > --Matt > > On Sat, Jul 7, 2012 at 6:32 PM, Konstantin Boudnik wrote: > > > Also, I have updated HADOOP-8417 against 1.1.0 and we need to include it. > > Otherwise, 1.1 will have the same issues for the downstream projects as > > 1.0.3 > > had. > > > > Cos > > > > On Sat, Jul 07, 2012 at 05:52PM, Konstantin Boudnik wrote: > > > Matt, > > > > > > Thanks for the update. > > > > > > HADOOP-8399 would be beneficial for BigTop release and it is marked for > > 1.1.0 > > > release. The patch is available for a while now and if someone can > > review I'd > > > go ahead and commit it today. > > > > > > I am working on the content of 0.3.1 BigTop release and will shortly > > post the > > > vote for it. Once Hadoop 1.1 rc is cut we'll start testing it with the > > rest of > > > the stack. > > > > > > Cos > > > > > > On Fri, Jul 06, 2012 at 02:24PM, Matt Foley wrote: > > > > Hi Cos, > > > > the query string didn't come thru on the link you sent, but the jira > > query > > > > I use is: > > > > project in (HADOOP,HDFS,MAPREDUCE) and (("Target Version/s" = > > '1.1.0' > > > > and (fixVersion != '1.1.0' or fixVersion is EMPTY)) or (fixVersion = > > > > '1.1.0' and "Target Version/s" is EMPTY)) and (status != Closed and > > status > > > > != Resolved) ORDER BY KEY > > > > > > > > You're correct that there are quite a few, currently 107, open jiras > > > > originally targeted for 1.1.0 that do not have committed fixes. Many > > of > > > > these are just the inherited backlog of previously identified work. > I > > need > > > > to move them to "Target Version/s" = 1.1.1. > > > > > > > > Folks have requested that the following currently open jiras be > > included in > > > > 1.1.0: > > > > > > > > HADOOP-8417 - HADOOP-6963 didn't update hadoop-core-pom-template.xml > > > > HADOOP-8445 - Token should not print the password in toString > > > > HDFS-96 - HDFS does not support blocks greater than 2GB > > > > HDFS-3596 - Improve FSEditLog pre-allocation in branch-1 > > > > MAPREDUCE-2903 - Map Tasks graph is throwing XML Parse error when Job > > is > > > > executed with 0 maps > > > > MAPREDUCE-2129 - Job may hang if > > > > mapreduce.job.committer.setup.cleanup.needed=false and > > > > mapreduce.map/reduce.failures.maxpercent>0 > > > > --- > > > > MAPREDUCE-4049 - plugin for generic shuffle service > > > > HADOOP-7823 - port HADOOP-4012 to branch-1 (splitting support for > > bzip2) > > > > > > > > The first six are simple patches that I am comfortable including. > > > > The last two are complex patches that have not yet been committed. > > > > I am planning to defer those two to 1.1.1. > > > > > > > > Beyond that, I'm going to cut 1.1.0-rc0 from the current state of > > > > branch-1.1. > > > > I'm planning to do that this weekend. This is obviously delayed from > > the > > > > previous plan, for which I apologize. > > > > > > > > Comments welcome. > > > > --Matt > > > > > > > > > > > > On Tue, Jul 3, 2012 at 8:32 PM, Konstantin Boudnik > > wrote: > > > > > > > > > Hi Matt. > > > > > > > > > > I am picking up the hat of BigTop's maintainer for Hadoop 1.x line. > > And I > > > > > wanted to sync up with about the Hadoop 1.1 release outlook, > > progress, > > > > > what help > > > > > you might need, etc. > > > > > > > > > > I see a few jiras left open in the release > > > > > http://is.gd/OyuaNQ > > > > > Is this the correct representation of the current status? > > > > > How I can help from BigTop side (I haven't yet finalized the > stack's > > > > > versions), etc. Looking forward for your input. Thanks. > > > > > > > > > > Cos > > > > > > > > > > On Fri, May 25, 2012 at 02:49PM, Matt Foley wrote: > > > > > > Greetings. With the approval of a public vote on common-dev@, I > > have > > > > > > branched Hadoop branch-1 to create branch-1.1. From this, I will > > create > > > > > a > > > > > > release candidate RC-0 for Hadoop-1.1.0, hopefully to be > available > > > > > shortly > > > > > > after this weekend. > > > > > > > > > > > > There are over 80 patches in branch-1, over and above the > contents > > of > > > > > > hadoop-1.0.3. So I anticipate that some stabilization will be > > needed, > > > > > > before the RC can be approved as a 1.1.0 release. Your > > participation in > > > > > > assuring a stable RC is very important. When it becomes > available, > > > > > please > > > > > > download it and work with it to determine whether it is stable > > enough to > > > > > > release, and report issues found. My colleagues and I will do > > likewise, > > > > > of > > > > > > course, but no one company can adequately exercise a new release > > with > > > > > this > > > > > > many new contributions. > > > > > > > > > > > > There are two outstanding issue that are not yet committed, but I > > know > > > > > the > > > > > > contributors hope to see in 1.1.0: > > > > > > MAPREDUCE-4049 < > > https://issues.apache.org/jira/browse/MAPREDUCE-4049 > > > > > > > > > > > > HADOOP-4012 < > https://issues.apache.org/jira/browse/HADOOP-4012 > > > > > > > > > Assuming there is an RC-1, and that these two patches can be > > committed > > > > > > during stabilization of RC-0, I will plan to incorporate these > > additional > > > > > > items in RC-1. > > > > > > > > > > > > Best regards, > > > > > > --Matt > > > > > > Release Manager > > > > > > > > > > > > -- http://hortonworks.com/download/ --20cf307f343ea381fc04c4a8e138--