Re: continuing releases on Apache Hadoop 2.6.x

+1, this sounds good to me. Thanks +Vinod > On Nov 25, 2015, at 11:44 AM, Junping Du wrote: > > May be we should quickly go through landed patches in 2.6.3 list and postpone > any risky patches to 2.6.4? >

Re: [VOTE] Release Apache Hadoop 2.7.2 RC0

I think we should get it in, I am still stuck on a couple of HDFS patches. But I was not sure overall if the patch was right. Commented on the JIRA regarding the same. Thanks +Vinod > On Nov 27, 2015, at 1:54 AM, Steve Loughran wrote: > > well, I'm not going to block

Re: Nightly Jenkins job for maintenance releases

FWIW when I used it during the 2.6.2 release (thanks Andrew for setting this up), the builds never finished completely due to memory issues. Some tuning and debugging would be needed to make this work reliably. Sangjin On Mon, Nov 30, 2015 at 11:18 AM, Andrew Wang

[jira] [Resolved] (HADOOP-12595) Remove the support of the deprecated dfs.umask

[ https://issues.apache.org/jira/browse/HADOOP-12595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li resolved HADOOP-12595. --- Resolution: Duplicate > Remove the support of the deprecated dfs.umask >

[jira] [Reopened] (HADOOP-12605) Fix intermittent failure of TestIPC.testIpcWithReaderQueuing

[ https://issues.apache.org/jira/browse/HADOOP-12605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masatake Iwasaki reopened HADOOP-12605: --- I rethought about this. It would be better to do follow-up work here because the patch

Jenkins build is back to normal : Hadoop-Common-trunk #2055

See

Re: Nightly Jenkins job for maintenance releases

I set up a parameterized branch-2 job during the 2.6.2 release process, so you can do on-demand builds there for whatever branch: https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-branch2-parameterized/ We already have a nightly branch-2 jobs and the set of flaky tests normally isn't

Nightly Jenkins job for maintenance releases

Hi, I'm helping Junping to get Hadoop 2.6.3 out of the door. Sanjin found out that there are some unit tests that are failing. I wonder, is it possible to set up some nightly Jenkins jobs for the maintenance lines so that we have better ideas on the quality of the releases? We can just turn it

Build failed in Jenkins: Hadoop-common-trunk-Java8 #756

See Changes: [jlowe] Update CHANGES.txt for commit of MR-6549 to branch-2.7 and branch-2.6. -- [...truncated 5802 lines...] Java HotSpot(TM) 64-Bit Server VM warning: ignoring option

Re: [DISCUSS] Looking to a 2.8.0 release

> > > maybe discuss having a list @ release time. As an example, s3 and > encryption at rest shipped in beta stage... what's in 2.8 that "we don't > yet trust ourselves?". Me, I'd put erasure coding in there just because > I've no familiarity with it > > Quick clarification, EC isn't scheduled

Re: Disable some of the Hudson integration comments on JIRA

Good point Allen. So I guess the broader question is, do we find the per-commit tracking build and test useful? With our current flakiness levels, there isn't much signal from a FAILED on one of these integration jobs. I think Hadoop-trunk-Commit is still nice as a compilation check. So overall

Re: Disable some of the Hudson integration comments on JIRA

+1. Colin On Mon, Nov 30, 2015 at 11:33 AM, Andrew Wang wrote: > Good point Allen. So I guess the broader question is, do we find the > per-commit tracking build and test useful? With our current flakiness > levels, there isn't much signal from a FAILED on one of these

Re: Disable some of the Hudson integration comments on JIRA

On Mon, Nov 30, 2015 at 3:04 PM, Allen Wittenauer wrote: > > > On Nov 30, 2015, at 11:33 AM, Andrew Wang > wrote: > > > > Good point Allen. So I guess the broader question is, do we find the > > per-commit tracking build and test useful? With our

[jira] [Created] (HADOOP-12608) Fix error message in WASB in connecting through Anonymous Credential codepath

Dushyanth created HADOOP-12608: -- Summary: Fix error message in WASB in connecting through Anonymous Credential codepath Key: HADOOP-12608 URL: https://issues.apache.org/jira/browse/HADOOP-12608 Project:

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

See Changes: [wang] HDFS-9470. Encryption zone on root not loaded from fsimage after NN -- [...truncated 5388 lines...] Running org.apache.hadoop.metrics2.lib.TestInterns Tests run: 4,

Build failed in Jenkins: Hadoop-common-trunk-Java8 #757

See Changes: [wang] HDFS-9470. Encryption zone on root not loaded from fsimage after NN -- [...truncated 5799 lines...] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:

Re: Disable some of the Hudson integration comments on JIRA

To be exhaustive, we'd also add the various -Drequire options for full inclusion of all optional native components. Unfortunately, that gets tricky because of the various build pre-requisites which would need to be present on the Jenkins hosts. This is where the Dockerfile is helpful, because it

Re: Disable some of the Hudson integration comments on JIRA

> On Nov 30, 2015, at 11:33 AM, Andrew Wang wrote: > > Good point Allen. So I guess the broader question is, do we find the > per-commit tracking build and test useful? With our current flakiness > levels, there isn't much signal from a FAILED on one of these

Re: Disable some of the Hudson integration comments on JIRA

I went ahead and turned off JIRA notification for all the "other" jobs I could find, if you see more than one Hudson email from now on feel free to ping me or turn it off yourself. The jobs are also still running, just not JIRA commenting anymore. I did also add the native nvn args to

Re: Disable some of the Hudson integration comments on JIRA

> On Nov 30, 2015, at 3:46 PM, Chris Nauroth wrote: > > To be exhaustive, we'd also add the various -Drequire options for full > inclusion of all optional native components. Unfortunately, that gets > tricky because of the various build pre-requisites which would need

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

See Changes: [aajisaka] HDFS-9336. deleteSnapshot throws NPE when snapshotname is null. -- [...truncated 5385 lines...] Running org.apache.hadoop.crypto.TestCryptoStreams Tests run: 14,

FOSDEM 2016 - take action by 4th of December 2015

As most of you probably know FOSDEM 2016 (the biggest, 100% free open source developer conference) is right around the corner: https://fosdem.org/2016/ We hope to have an ASF booth and we would love to see as many ASF projects as possible present at various tracks (AKA Developer rooms):

Build failed in Jenkins: Hadoop-common-trunk-Java8 #758

See Changes: [aajisaka] HDFS-9336. deleteSnapshot throws NPE when snapshotname is null. -- [...truncated 5789 lines...] Tests run: 25, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: