Build failed in Jenkins: Hadoop-Common-0.23-Build #212

See Changes: [bobby] svn merge -c 1308566 from trunk. FIXES MAPREDUCE-4024. RM webservices can't query on finalStatus (Tom Graves via bobby) [tgraves] merge -r 1308532:1308533 from branch-2. FIXES: MAPREDUCE-4089 [bobby] svn

Build failed in Jenkins: Hadoop-Common-trunk #366

See Changes: [suresh] HDFS-3126. Journal stream from Namenode to BackupNode needs to have timeout. Contributed by Hari Mankude. [eli] HDFS-3148. The client should be able to use multiple local interfaces for data transfer. Contrib

Re: [VOTE] Hadoop-1.0.2-rc2

I am +1, of course. Candidate passed my team's system test. --Matt (Release Manager) On Mon, Apr 2, 2012 at 7:42 PM, Mahadev Konar wrote: > +1 downloaded the release and installed it. Ran sleep job/random > writer on a single node. > > thanks > mahadev > > On Mon, Apr 2, 2012 at 7:03 PM, Devaraj

Help a newbie on patch submission

Hi, I'm trying to submit a patch to fix some build problems in Hadoop trunk on Windows, and I'm having a hard time pleasing Hadoop QA. This is for Hadoop-8241 (https://issues.apache.org/jira/browse/HADOOP-8241). I submitted the first patch and it said it couldn't apply it, so I figured it may ha

RE: Help a newbie on patch submission

I tried applying your patches in my environment, It works fine. The issue with Hadoop QA may be because of having -M (^M) characters in the patch file. Can you try by removing the -M (^M) chars in the patch. Thanks Devaraj From: Mostafa Elhemali [mosta

RE: Help a newbie on patch submission

Thanks Devaraj. I actually took care to convert the line endings to just LINE FEED (0A/^J) before submission, and I don't see ^M characters in either patch. I just opened the files in a binary editor to double-check and I don't see 0D anywhere. -Original Message- From: Devaraj k [mailto

Re: Help a newbie on patch submission

I believe the issue is that the Hadoop QA bot runs from a subdirectory of the project root, i.e. hadoop-common-project, hadoop-hdfs-project, etc. Your patch only changes things under hadoop-dist, so I don't think it will work no matter how you format the patch. For this particular JIRA (HADOOP-824

RE: Help a newbie on patch submission

Thanks Aaron - that makes sense. Will do that. -Original Message- From: Aaron T. Myers [mailto:a...@cloudera.com] Sent: Tuesday, April 03, 2012 10:20 AM To: common-dev@hadoop.apache.org Subject: Re: Help a newbie on patch submission I believe the issue is that the Hadoop QA bot runs from

Re: [RESULT] - [VOTE] Rename hadoop branches post hadoop-1.x

Arun, I am even more confused now than I was before: Here you say: > Essentially 'trunk' is where incompatible changes *may* be committed (in >future). We should allow for that. On another thread, responding to Avner (re: MAPREDUCE-4049?) you say, > We do expect 'new features' to make it to t

[jira] [Created] (HADOOP-8244) Improve comments on ByteBufferReadable.read

Improve comments on ByteBufferReadable.read --- Key: HADOOP-8244 URL: https://issues.apache.org/jira/browse/HADOOP-8244 Project: Hadoop Common Issue Type: Improvement Reporter: Henry Robins

Re: [RESULT] - [VOTE] Rename hadoop branches post hadoop-1.x

Hi Milind, On Tue, Apr 3, 2012 at 11:27 AM, wrote: > Here you say: > > > > Essentially 'trunk' is where incompatible changes *may* be committed (in > >future). We should allow for that. > What I believe Arun is alluding to here is that we expect for compatibility to be maintained for the lifeti

Re: [RESULT] - [VOTE] Rename hadoop branches post hadoop-1.x

Thanks ATM. I guess the "*may*" emphasis confused me. Just to get some more clarity: What would be guideline for a new feature, such as https://issues.apache.org/jira/browse/MAPREDUCE-4049, which maintains compatibility for 1.x, but is not relevant to trunk, because the codebases have completely

Re: [RESULT] - [VOTE] Rename hadoop branches post hadoop-1.x

On Tue, Apr 3, 2012 at 2:37 PM, wrote: > What would be guideline for a new feature, such as > https://issues.apache.org/jira/browse/MAPREDUCE-4049, which maintains > compatibility for 1.x, but is not relevant to trunk, because the codebases > have completely diverged, so cannot be committed to tr

Re: [RESULT] - [VOTE] Rename hadoop branches post hadoop-1.x

To my knowledge, shuffle is already pluggable in 0.23 onwards, as long as it is used only by mapreduce framework. That's why Avner says : "In parallel, I'll try to *learn what exists* in 0.23". (Emphasize my own.) That's why I was wondering about the insistence of committing to trunk first. - Mi

Re: [RESULT] - [VOTE] Rename hadoop branches post hadoop-1.x

If that's the case then there doesn't seem to be any question here. The feature is in trunk, and an implementation could be done for an older release branch that would be compatible with that branch. Sure, the code to implement the feature is quite different between the two branches, but trunk will

Re: [RESULT] - [VOTE] Rename hadoop branches post hadoop-1.x

Great ! Thanks @atm, - milind On 4/3/12 3:21 PM, "Aaron T. Myers" wrote: >If that's the case then there doesn't seem to be any question here. The >feature is in trunk, and an implementation could be done for an older >release branch that would be compatible with that branch. Sure, the code >to

[jira] [Resolved] (HADOOP-8215) Security support for ZK Failover controller

[ https://issues.apache.org/jira/browse/HADOOP-8215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved HADOOP-8215. - Resolution: Fixed Fix Version/s: Auto Failover (HDFS-3042) Hadoop Flags: Reviewed

Re: [VOTE] Hadoop-1.0.2-rc2

+1 Sigs check out. I ran some sample jobs. Arun On Mar 27, 2012, at 11:52 AM, Matt Foley wrote: > Aaron, > Under current rules, I think we have to restart the vote. Later this > afternoon I'll post a proposal for a change in these rules, because I agree > with you we should try to accelerate t

[jira] [Created] (HADOOP-8245) Fix flakiness in TestZKFailoverController

Fix flakiness in TestZKFailoverController - Key: HADOOP-8245 URL: https://issues.apache.org/jira/browse/HADOOP-8245 Project: Hadoop Common Issue Type: Bug Components: auto-failover, ha Af

[jira] [Created] (HADOOP-8246) Auto-HA: automatically scope znode by nameservice ID

Auto-HA: automatically scope znode by nameservice ID Key: HADOOP-8246 URL: https://issues.apache.org/jira/browse/HADOOP-8246 Project: Hadoop Common Issue Type: Improvement Compon