Re: Release numbering for branch-2 releases

On Mon, Feb 4, 2013 at 10:46 AM, Arun C Murthy wrote: > > On Feb 1, 2013, at 2:34 AM, Tom White wrote: > > Whereas Arun is proposing > > > > 2.0.0-alpha, 2.0.1-alpha, 2.0.2-alpha, 2.1.0-alpha, 2.2.0-beta, 2.3.0 > > > > and the casual observer might expect there to be a stable 2.0.1 (say) > > on

Re: Release numbering for branch-2 releases

On Mon, Feb 4, 2013 at 1:07 PM, Owen O'Malley wrote: > I think that using "-(alpha,beta)" tags on the release versions is a really > bad idea. Why? Can you please share some reasons? I actually think alpha and beta and stable/GA are much better way to set the expectation of the quality of a re

Heads up - merge branch-trunk-win to trunk

The support for Hadoop on Windows was proposed in HADOOP-8079 almost a year ago. The goal was to make Hadoop natively integrated, full-featured, and performance and scalability tuned on Windows Server or Windows Azure. We are happy to announce that

Re: [Vote] Merge branch-trunk-win to trunk

e able to run nightly tests to > > validate everything still compiles/runs. This is not a blocker for me > > because we often rely on individuals and groups to test Hadoop, but I do > > think we need to have this discussion before we put it in. > > > > --Bobby > >

Re: [Vote] Merge branch-trunk-win to trunk

> It seems that with the HW in place, the matter of setting at least nightly > build is trivial for anyone with up to date Windows knowledge. I wish I > could > help. Going without a validation is a recipe for a disaster IMO. > > -1 until some reasonable solution is implemented. > Cos Cos, I ha

Re: [Vote] Merge branch-trunk-win to trunk

Thank you all for voting and participating in the discussions. With 11 +1s from committers (more than the required 3 +1s from active committers per the Hadoop bylaws), 1 +0, 8 +1s from other contributors, and no -1s the merge vote passes. I have committed the consolidated patch from branch-trunk-

Re: [Vote] Merge branch-trunk-win to trunk

Cos, There is progress being made on that ticket. Also it has nothing to do with that. Please follow the discussion here and why this happened due to an invalid commit that was reverted - https://issues.apache.org/jira/browse/HDFS-4615?focusedCommentId=13612650&page=com.atlassian.jira.plugin.syst

Re: [Vote] Merge branch-trunk-win to trunk

Adding other mailing lists I missed earlier. Cos, There is progress being made on that ticket. Also it has nothing to do with that. Please follow the discussion here and why this happened due to an invalid commit that was reverted - https://issues.apache.org/jira/browse/HDFS-4615?focusedComment

Re: Heads up - 2.0.5-beta

Thanks for starting this discussion. I volunteer to do a final review of protocol changes, so we can avoid incompatible changes to API and wire protocol post 2.0.5 in Common and HDFS. We have been working really hard on the following features. I would like to get into 2.x and see it reach HDFS use

Re: Heads up - 2.0.5-beta

Eli, I will post a more detailed reply soon. But one small correction: I'm also not sure there's currently consensus on what an incompatible > change is. For example, I think HADOOP-9151 is incompatible because it > broke client/server wire compatibility with previous releases and any > change th

Re: [VOTE] Release Apache Hadoop 2.1.1-beta

+1 (binding) Verified the signatures and hashes for both src and binary tars. Built from the source, the binary distribution and the documentation. Started a single node cluster and tested the following: # Started HDFS cluster, verified the hdfs CLI commands such ls, copying data back and forth,

Re: 2.1.2 (Was: Re: [VOTE] Release Apache Hadoop 2.1.1-beta)

I am +1 for naming the new branch 2.2.0. On Tue, Oct 1, 2013 at 4:15 PM, Arun C Murthy wrote: > Guys, > > I took a look at the content in 2.1.2-beta so far, other than the > critical fixes such as HADOOP-9984 (symlinks) and few others in YARN/MR, > there is fairly little content (unit tests fi

Re: 2.1.2 (Was: Re: [VOTE] Release Apache Hadoop 2.1.1-beta)

(This time copying all the lists) I am +1 for naming the new branch 2.2.0. On Tue, Oct 1, 2013 at 4:15 PM, Arun C Murthy wrote: > Guys, > > I took a look at the content in 2.1.2-beta so far, other than the > critical fixes such as HADOOP-9984 (symlinks) and few others in YARN/MR, > there is f

Re: [VOTE] Release Apache Hadoop 2.2.0

+1 (binding) On Mon, Oct 7, 2013 at 12:00 AM, Arun C Murthy wrote: > Folks, > > I've created a release candidate (rc0) for hadoop-2.2.0 that I would like > to get released - this release fixes a small number of bugs and some > protocol/api issues which should ensure they are now stable and will

Re: Thinking ahead to 2.4

Arun, Some of the previously 2.4 targeted features were made available in 2.3: - Heterogeneous storage support - Datanode cache The following are being targeted for 2.4: - Use protobuf for fsimge (already in) - ACLs (in trunk. In a week or so, this will be merged to branch-2.4) - Rolling upgrades

Re: [VOTE] Release Apache Hadoop 2.4.0

+1 (binding) Verified the signatures and hashes for both src and binary tars. Built from the source, the binary distribution and the documentation. Started a single node cluster and tested the following: # Started HDFS cluster, verified the hdfs CLI commands such ls, copying data back and forth, v

Re: hadoop-2.5 - June end?

We should also include extended attributes feature for HDFS from HDFS-2006 for release 2.5. On Mon, Jun 9, 2014 at 9:39 AM, Arun C Murthy wrote: > Folks, > > As you can see from the Roadmap wiki, it looks like several items are > still a bit away from being ready. > > I think rather than wait

Re: Updates on migration to git

Karthik, I would like to see detailed information on how this migration will be done, how it will affect the existing project and commit process. This should be done in a document that can be reviewed instead of in an email thread on an ad-hoc basis. Was there any voting on this in PMC and should

Re: Updates on migration to git

, Suresh Srinivas wrote: > Karthik, > > I would like to see detailed information on how this migration will be > done, how it will affect the existing project and commit process. This > should be done in a document that can be reviewed instead of in an email > thread on an ad-ho

Re: Thinking ahead to hadoop-2.6

I actually would like to see both archival storage and single replica memory writes to be in 2.6 release. Archival storage is in the final stages of getting ready for branch-2 merge as Nicholas has already indicated on the dev mailing list. Hopefully HDFS-6581 gets ready sooner. Both of these featu

Re: Thinking ahead to hadoop-2.6

es specified > by > > storage policies assigned to the files/directories. Cluster admin could > > disable the feature by simply not configuring any storage type and not > > setting any storage policy as before. As Suresh mentioned, HDFS-6584 is > > in the final stages

Re: [VOTE] Release Apache Hadoop 2.6.0

Tsuyoshi, thanks for bringing up HDFS-6833. However, given it is a boundary condition (and should not cause issues when for files with replication factor 3), we should perhaps target this into 2.6.1 and not block this release. Thoughts? On Mon, Nov 17, 2014 at 4:17 AM, Tsuyoshi OZAWA wrote: > +0

Re: [VOTE] Release Apache Hadoop 2.6.0

+1 (binding) Verified the signatures and hashes for both src and binary tars. Built from the source, the binary distribution and the documentation. Started a single node cluster and tested the following: - Started HDFS cluster, verified the hdfs CLI commands such ls, copying data back and forth, v

Re: [VOTE] Merge MR-279 to trunk.

+1.

[jira] [Resolved] (MAPREDUCE-4657) WindowsResourceCalculatorPlugin has NPE

[ https://issues.apache.org/jira/browse/MAPREDUCE-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas resolved MAPREDUCE-4657. Resolution: Fixed Fix Version/s: 1-win Hadoop Flags: Reviewed +1

[jira] [Resolved] (MAPREDUCE-4739) Some MapReduce tests fail to find winutils.

[ https://issues.apache.org/jira/browse/MAPREDUCE-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas resolved MAPREDUCE-4739. Resolution: Fixed +1 for the patch. I committed it. Thank you Chris for the

[jira] [Resolved] (MAPREDUCE-4780) MapReduce distribution build fails on Windows

[ https://issues.apache.org/jira/browse/MAPREDUCE-4780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas resolved MAPREDUCE-4780. Resolution: Fixed Fix Version/s: trunk-win Hadoop Flags: Reviewed

[jira] [Resolved] (MAPREDUCE-4790) MapReduce build script would be more readable using abspath

[ https://issues.apache.org/jira/browse/MAPREDUCE-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas resolved MAPREDUCE-4790. Resolution: Fixed Fix Version/s: trunk-win Hadoop Flags: Reviewed

[jira] [Resolved] (MAPREDUCE-2355) Add an out of band heartbeat damper

[ https://issues.apache.org/jira/browse/MAPREDUCE-2355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas resolved MAPREDUCE-2355. Resolution: Fixed Fix Version/s: 0.20.203.0 Hadoop Flags: Reviewed

[jira] [Resolved] (MAPREDUCE-4909) TestKeyValueTextInputFormat fails with Open JDK 7 on Windows

[ https://issues.apache.org/jira/browse/MAPREDUCE-4909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas resolved MAPREDUCE-4909. Resolution: Fixed Hadoop Flags: Reviewed I committed the patch. Thank

[jira] [Resolved] (MAPREDUCE-4914) TestMiniMRDFSSort fails with openJDK7

[ https://issues.apache.org/jira/browse/MAPREDUCE-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas resolved MAPREDUCE-4914. Resolution: Fixed Fix Version/s: 1.2.0 Hadoop Flags: Reviewed +1

[jira] [Resolved] (MAPREDUCE-4915) TestShuffleExceptionCount fails with open JDK7

[ https://issues.apache.org/jira/browse/MAPREDUCE-4915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas resolved MAPREDUCE-4915. Resolution: Fixed Fix Version/s: 1.2.0 Hadoop Flags: Reviewed +1

[jira] [Created] (MAPREDUCE-4928) Use token request messages defined in hadoop common

Suresh Srinivas created MAPREDUCE-4928: -- Summary: Use token request messages defined in hadoop common Key: MAPREDUCE-4928 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4928 Project

[jira] [Resolved] (MAPREDUCE-3980) mr-jobhistory-daemon.sh should look for mapred script in HADOOP_MAPRED_HOME

[ https://issues.apache.org/jira/browse/MAPREDUCE-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas resolved MAPREDUCE-3980. Resolution: Duplicate Fix Version/s: 2.0.2-alpha Resolving it as

[jira] [Resolved] (MAPREDUCE-3635) Improve Hadoop subcomponent integration in Hadoop 0.23

[ https://issues.apache.org/jira/browse/MAPREDUCE-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas resolved MAPREDUCE-3635. Resolution: Duplicate This is already handled as a part of HADOOP-7939

[jira] Created: (MAPREDUCE-2276) Fix build failure introduced by HDFS-1547

Reporter: Suresh Srinivas Assignee: Suresh Srinivas Fix For: 0.23.0 MiniDFSCluster#startDataNodes() method signature changes introduced by HDFS-1547 breaks the mapreduce build -- This message is automatically generated by JIRA. - You can reply to this email to add

[jira] [Created] (MAPREDUCE-2467) HDFS-1052 changes break the raid contrib module in MapReduce

: Bug Components: contrib/raid Affects Versions: 0.23.0 Reporter: Suresh Srinivas Assignee: Suresh Srinivas Fix For: 0.23.0 Raid contrib module requires changes to work with the federation changes made in HDFS-1052. -- This message is automatically

[jira] [Created] (MAPREDUCE-2475) Disable IPV6 for junit tests

Reporter: Suresh Srinivas Assignee: Suresh Srinivas Fix For: 0.23.0 IPV6 addresses not handles currently in the common library methods. IPV6 can return address as "0:0:0:0:0:0:port". Some utility methods such as NetUtils#createSocketAddress()

[jira] [Resolved] (MAPREDUCE-2465) HDFS raid not compiling after federation merge

[ https://issues.apache.org/jira/browse/MAPREDUCE-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas resolved MAPREDUCE-2465. Resolution: Not A Problem MAPREDUCE-2467 fixed the build issue and reverted

[jira] [Resolved] (MAPREDUCE-4399) Fix performance regression in shuffle

[ https://issues.apache.org/jira/browse/MAPREDUCE-4399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas resolved MAPREDUCE-4399. Resolution: Fixed Hadoop Flags: Reviewed I committed the patch to branch

[jira] [Created] (MAPREDUCE-3204) mvn site:site fails on MapReduce

: 0.24.0 Reporter: Suresh Srinivas This problem does not happen on 0.23. See details in the next comment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure

[jira] [Created] (MAPREDUCE-3545) Remove Avro RPC

Remove Avro RPC --- Key: MAPREDUCE-3545 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3545 Project: Hadoop Map/Reduce Issue Type: Bug Reporter: Suresh Srinivas Assignee: Suresh Srinivas

[jira] [Created] (MAPREDUCE-3855) TestSubmitJob should use DistributedFileSystem

: test Affects Versions: 0.24.0 Reporter: Suresh Srinivas Priority: Minor TestSubmitJob uses ClientNamenodeProtocolTranslatorPB which is marked InterfaceAudience.Private. This causes build failures in mapreduce when HDFS changes internal/private classes. Test should be