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

See

RE: Replacing Commons-httpclient and bumping httpclient version

Thanks Wei-Chiu Chuang for initiating discussion here. I'm +1 too to clean up dependency on commons-httpclient. -Original Message- From: Masatake Iwasaki [mailto:iwasak...@oss.nttdata.co.jp] Sent: 17 February 2016 22:52 To: common-dev@hadoop.apache.org Subject: Re: Replacing Commons-http

Re: Looking to a Hadoop 3 release

+1 for the 3.0 release plan and continuing 2.x releases. I'm thinking we should consider stopping new 2.x minor releases after 3.x reaches GA. Thanks, Akira On 2/19/16 10:33, Gangumalla, Uma wrote: Yes. I think starting 3.0 release with alpha is good idea. So it would get some time to reach t

Re: Looking to a Hadoop 3 release

Hi Kai, Sure, I'm open to it. It's a new major release, so we're allowed to make these kinds of big changes. The idea behind the extended alpha cycle is that downstreams can give us feedback. This way if we do anything too radical, we can address it in the next alpha and have downstreams re-test.

Re: Looking to a Hadoop 3 release

Another thing to throw in there is the dependency/classpath isolation (HADOOP-11656). Some efforts have already been made by Sean, and it'd be great to complete this to have a much better dependency isolation solution for 3.x. On Thu, Feb 18, 2016 at 5:33 PM, Gangumalla, Uma wrote: > Yes. I thin

[jira] [Created] (HADOOP-12826) Rename the new Java coder and make it default

Rui Li created HADOOP-12826: --- Summary: Rename the new Java coder and make it default Key: HADOOP-12826 URL: https://issues.apache.org/jira/browse/HADOOP-12826 Project: Hadoop Common Issue Type: Sub

Re: Looking to a Hadoop 3 release

Yes. I think starting 3.0 release with alpha is good idea. So it would get some time to reach the beta or GA. +1 for the plan. For the compatibility purposes and as current stable versions, we should continue 2.x releases anyway. Thanks Andrew for starting the thread. Regards, Uma On 2/18/16,

RE: Looking to a Hadoop 3 release

Thanks Andrew for driving this. Wonder if it's a good chance for HADOOP-12579 (Deprecate and remove WriteableRPCEngine) to be in. Note it's not an incompatible change, but feel better to be done in the major release. Regards, Kai -Original Message- From: Andrew Wang [mailto:andrew.w...@

[jira] [Created] (HADOOP-12825) Log slow name resolutions

Sidharta Seethana created HADOOP-12825: -- Summary: Log slow name resolutions Key: HADOOP-12825 URL: https://issues.apache.org/jira/browse/HADOOP-12825 Project: Hadoop Common Issue Type:

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

See Changes: [cnauroth] HADOOP-11031. Design Document for Credential Provider API. Contributed -- [...truncated 3819 lines...] Generating

Jenkins build is back to normal : Hadoop-common-trunk-Java8 #1100

See

[jira] [Created] (HADOOP-12824) Collect network usage on the node in Windows

Inigo Goiri created HADOOP-12824: Summary: Collect network usage on the node in Windows Key: HADOOP-12824 URL: https://issues.apache.org/jira/browse/HADOOP-12824 Project: Hadoop Common Issue

[jira] [Created] (HADOOP-12823) Collect disks usage on the node in Windows

Inigo Goiri created HADOOP-12823: Summary: Collect disks usage on the node in Windows Key: HADOOP-12823 URL: https://issues.apache.org/jira/browse/HADOOP-12823 Project: Hadoop Common Issue Ty

Re: Looking to a Hadoop 3 release

Hi Kihwal, I think there's still value in continuing the 2.x releases. 3.x comes with the incompatible bump to a JDK8 runtime, and also the fact that 3.x won't be beta or GA for some number of months. In the meanwhile, it'd be good to keep putting out regular, stable 2.x releases. Best, Andrew

Re: Looking to a Hadoop 3 release

Moving Hadoop 3 forward sounds fine. If EC is one of the main motivations, are we getting rid of branch-2.8? Kihwal From: Andrew Wang To: "common-dev@hadoop.apache.org" Cc: "yarn-...@hadoop.apache.org" ; "mapreduce-...@hadoop.apache.org" ; hdfs-dev Sent: Thursday, February 18, 201

Re: Looking to a Hadoop 3 release

Hi all, Reviving this thread. I've seen renewed interest in a trunk release since HDFS erasure coding has not yet made it to branch-2. Along with JDK8, the shell script rewrite, and many other improvements, I think it's time to revisit Hadoop 3.0 release plans. My overall plan is still the same a

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

See

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

See Changes: [rkanter] HADOOP-12817. Enable TLS v1.1 and 1.2 (rkanter) [kihwal] HDFS-4946. Allow preferLocalNode in BlockPlacementPolicyDefault to be [szetszwo] HADOOP-10865. Add a Crc32 chunked verification benchmark for bo

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

See Changes: [cnauroth] HDFS-9711. Integrate CSRF prevention filter in WebHDFS. Contributed by [rkanter] HADOOP-12817. Enable TLS v1.1 and 1.2 (rkanter) [kihwal] HDFS-4946. Allow preferLocalNode in BlockPlacementPolicyDefault to

Jenkins build is back to normal : Hadoop-common-trunk-Java8 #1097

See

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

See Changes: [aajisaka] HDFS-6832. Fix the usage of 'hdfs namenode' command. Contributed by -- [...truncated 3819 lines...] Generating

[jira] [Created] (HADOOP-12822) Change "Metrics intern cache overflow" log level from WARN to INFO

Akira AJISAKA created HADOOP-12822: -- Summary: Change "Metrics intern cache overflow" log level from WARN to INFO Key: HADOOP-12822 URL: https://issues.apache.org/jira/browse/HADOOP-12822 Project: Had

[jira] [Created] (HADOOP-12821) Change "Auth successful" audit log level from info to debug

Yong Zhang created HADOOP-12821: --- Summary: Change "Auth successful" audit log level from info to debug Key: HADOOP-12821 URL: https://issues.apache.org/jira/browse/HADOOP-12821 Project: Hadoop Common

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

See

[jira] [Resolved] (HADOOP-12820) build order might be wrong, cannot find artifact org.apache.hadoop:hadoop-auth:jar:tests:3.0.0-SNAPSHOT

[ https://issues.apache.org/jira/browse/HADOOP-12820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinayakumar B resolved HADOOP-12820. Resolution: Invalid > build order might be wrong, cannot find artifact > org.apache.hadoo

[jira] [Created] (HADOOP-12820) build order might be wrong, cannot find artifact org.apache.hadoop:hadoop-auth:jar:tests:3.0.0-SNAPSHOT

james michael dupont created HADOOP-12820: - Summary: build order might be wrong, cannot find artifact org.apache.hadoop:hadoop-auth:jar:tests:3.0.0-SNAPSHOT Key: HADOOP-12820 URL: https://issues.apache.org

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

See Changes: [rohithsharmaks] YARN-4654. Yarn node label CLI should parse "=" correctly when trying to [vvasudev] MAPREDUCE-6634. Log uncaught exceptions/errors in various thread pools -