Re: [ANNOUNCE] Intend to build a 0.20.205.1 candidate next Friday 11 Nov.

> I had spoken with Sanjay offline about this patch a week or so before > 205 was frozen. At that point we had left the discussion that we would > try to get it in for 205 with the understanding that a trunk patch > would be posted within a day or two of the 205 patch. Given that it's > now been a

Re: [ANNOUNCE] Intend to build a 0.20.205.1 candidate next Friday 11 Nov.

Hey guys, HDFS-2246 is not a fix, it's a non-trivial performance optimization. The roadmap page is pretty clear.. "Point releases are made to fix critical bugs. They do not introduce new features or make other improvements other than fixing bugs". I'm not opposed to the change, I'm just pointing

Re: [ANNOUNCE] Intend to build a 0.20.205.1 candidate next Friday 11 Nov.

On Thu, Nov 10, 2011 at 9:58 PM, Suresh Srinivas wrote: > Eli, > > As Jitendra indicated in the jira, this was originally supposed to be part > of 0.205. Due to time crunc, we could not get this done in 0.205. This can > be turned off by a flag and only can be enabled by users who want to use > th

Re: [ANNOUNCE] Intend to build a 0.20.205.1 candidate next Friday 11 Nov.

Eli, As Jitendra indicated in the jira, this was originally supposed to be part of 0.205. Due to time crunc, we could not get this done in 0.205. This can be turned off by a flag and only can be enabled by users who want to use the functionality. Given that, I feel it is okay to go into 0.205.1.

Re: [ANNOUNCE] Intend to build a 0.20.205.1 candidate next Friday 11 Nov.

Hi Eli, There is no new functionality added by HDFS-2246. It is a "performance" fix. But I agree that it is not a trivial fix. One proposal coud be to commit this patch to trunk too and then continue to work on HDFS-347 to make a better fix to this problem. The godo part is that there is no API c

[jira] [Resolved] (HADOOP-7751) rpm version is not being picked from the -Dversion option in 205

[ https://issues.apache.org/jira/browse/HADOOP-7751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Yang resolved HADOOP-7751. --- Resolution: Won't Fix For maven, the number number includes -SNAPSHOT for on going builds. Unfortu

Re: [ANNOUNCE] Intend to build a 0.20.205.1 candidate next Friday 11 Nov.

Hey Matt, Is HDFS-2246 slated for 0.20.205.1? Given that it's not a bug and is non-trivial it seems better suited for 206 than a point release. Also, per the sustaining roadmap - http://wiki.apache.org/hadoop/Roadmap - "Only functionality already committed to trunk should be submitted to a sustai

[jira] [Created] (HADOOP-7815) Map memory mb is being incorrectly set by hadoop-setup-conf.sh

Map memory mb is being incorrectly set by hadoop-setup-conf.sh -- Key: HADOOP-7815 URL: https://issues.apache.org/jira/browse/HADOOP-7815 Project: Hadoop Common Issue Type: Bug

[jira] [Created] (HADOOP-7814) Add ability to add the contents of a properties file to Configuration

Add ability to add the contents of a properties file to Configuration - Key: HADOOP-7814 URL: https://issues.apache.org/jira/browse/HADOOP-7814 Project: Hadoop Common Issue

[jira] [Created] (HADOOP-7813) test-patch +1 patches that introduce javadoc and findbugs warnings in somecases

test-patch +1 patches that introduce javadoc and findbugs warnings in somecases --- Key: HADOOP-7813 URL: https://issues.apache.org/jira/browse/HADOOP-7813 Project: Hadoop Com

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

See Changes: [vinodkv] MAPREDUCE-. Fixed bugs in ContainerLauncher of MR AppMaster due to which per-container connections to NodeManager were lingering long enough to hit the ulimits on number of processes. (vinodkv) svn