[jira] [Created] (HADOOP-11668) start-dfs.sh and stop-dfs.sh no longer works in HA mode after --slaves shell option

2015-03-03 Thread Vinayakumar B (JIRA)
Vinayakumar B created HADOOP-11668: -- Summary: start-dfs.sh and stop-dfs.sh no longer works in HA mode after --slaves shell option Key: HADOOP-11668 URL: https://issues.apache.org/jira/browse/HADOOP-11668

[jira] [Resolved] (HADOOP-6857) FsShell should report raw disk usage including replication factor

2015-03-03 Thread Akira AJISAKA (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA resolved HADOOP-6857. --- Resolution: Fixed Fix Version/s: (was: 2.7.0) 3.0.0 Moved the s

[jira] [Created] (HADOOP-11667) Improve Credentials class for thread safe to avoid corruption for shared credentials between Jobs.

2015-03-03 Thread zhihai xu (JIRA)
zhihai xu created HADOOP-11667: -- Summary: Improve Credentials class for thread safe to avoid corruption for shared credentials between Jobs. Key: HADOOP-11667 URL: https://issues.apache.org/jira/browse/HADOOP-11667

[jira] [Created] (HADOOP-11666) Revert the format change of du output introduced by HADOOP-6853

2015-03-03 Thread Akira AJISAKA (JIRA)
Akira AJISAKA created HADOOP-11666: -- Summary: Revert the format change of du output introduced by HADOOP-6853 Key: HADOOP-11666 URL: https://issues.apache.org/jira/browse/HADOOP-11666 Project: Hadoop

Re: Looking to a Hadoop 3 release

2015-03-03 Thread Arun Murthy
Awesome, looks like we can just do this in a compatible manner - nothing else on the list seems like it warrants a (premature) major release. Thanks Vinod. Arun From: Vinod Kumar Vavilapalli Sent: Tuesday, March 03, 2015 2:30 PM To: common-dev@hadoop.ap

Re: Looking to a Hadoop 3 release

2015-03-03 Thread Vinod Kumar Vavilapalli
I started pitching in more on that JIRA. To add, I think we can and should strive for doing this in a compatible manner, whatever the approach. Marking and calling it incompatible before we see proposal/patch seems premature to me. Commented the same on JIRA: https://issues.apache.org/jira/bro

[jira] [Reopened] (HADOOP-6857) FsShell should report raw disk usage including replication factor

2015-03-03 Thread Akira AJISAKA (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA reopened HADOOP-6857: --- We still need to do either of the below things * Move the section in CHANGES.txt to incompatible

Re: Looking to a Hadoop 3 release

2015-03-03 Thread Allen Wittenauer
Between: * removing -finalize * breaking HDFS browsing * changing du’s output (in the 2.7 branch) * changing various names of metrics (either intentionally or otherwise) * changing the JDK release … and probably lots of other stuff in branch-2 I hav

Re: Looking to a Hadoop 3 release

2015-03-03 Thread Vinod Kumar Vavilapalli
Totally agreed. I just left a comment there on the current state and what is needed. As of now, I think the big (and only?) changes are flipping the default classloader for tasks and splitting the HDFS jar. Thanks, +Vinod On Mar 3, 2015, at 9:02 AM, Steve Loughran mailto:ste...@hortonworks.com

Re: Looking to a Hadoop 3 release

2015-03-03 Thread sanjay Radia
> On Mar 3, 2015, at 9:36 AM, Karthik Kambatla wrote: > > If we preserve API compat and try to preserve wire compat, I don't see the > harm in bumping the major release. If we preserve compatibility, then there is no need to bump major number. > It allows us to include several > fixes/features

Re: Looking to a Hadoop 3 release

2015-03-03 Thread Karthik Kambatla
I am surprised classpath-isolation is being called a minor issue. We have been hearing users complain about Hadoop leaking its dependencies into the classpath for a while now, Guava being the culprit often. Not being able to upgrade our dependencies without affecting users has started to hamper our

Re: Looking to a Hadoop 3 release

2015-03-03 Thread Steve Loughran
I want to understand a lot more about the classpath isolation (HADOOP-11656) proposal, specifically, what is proposed and does it have to be tagged as incompatible? That's a bigger change than must setting javac.version=8 in the POM —though given what a fundamental problem it addresses, I'm in

timsort bug in the JDK

2015-03-03 Thread Steve Loughran
One other late-breaking issue may we "what to do about the fact that Java 7 & 8 have a broken sort algorithm?, which has surfaced recently I believe some other OSS projects have tried to ad

Re: Looking to a Hadoop 3 release

2015-03-03 Thread Andrew Wang
Hi Junping, thanks for your response, I view branch-3 as essentially the same size as our recent 2.x releases, with the exception of incompatible changes like classpath isolation and JDK8 target version. These, while perhaps not revolutionary, are still incompatible, and require a major version bu

Re: Looking to a Hadoop 3 release

2015-03-03 Thread Andrew Wang
Hi Akira, thanks for responding, On Tue, Mar 3, 2015 at 4:04 AM, Akira AJISAKA wrote: > Thanks Andrew for bringing this up. > +1 mostly looks fine but I'm thinking it's not now to cut branch-3. > > > classpath isolation > > IMHO, classpath isolation is a good thing to do. > We should pay down th

Re: Looking to a Hadoop 3 release

2015-03-03 Thread Andrew Wang
Hi Konst, thanks for taking a look. I think I essentially agree with your points. On Mon, Mar 2, 2015 at 11:04 PM, Konstantin Shvachko wrote: > Andrew, > > Hadoop 3 seems in general like a good idea to me. > 1. I did not understand if you propose to release 3.0 instead of 2.7 or in > addition? >

Re: Looking to a Hadoop 3 release

2015-03-03 Thread Junping Du
Thanks all for good discussions here. +1 on supporting Java 8 ASAP. In addition, I agree that we should separating this effort with cutting down Hadoop 3. IMO, Hadoop is still very cool today, and we should only consider Hadoop 3 until we have revolutionary feature (like YARN for 2.0) which dese

Re: The Activities of Apache Hadoop Community

2015-03-03 Thread Akira AJISAKA
Hi all, One year after the previous post, we collected and analyzed JIRA tickets again to investigate the activities of Apache Hadoop community in 2014. http://ajisakaa.blogspot.com/2015/02/the-activities-of-apache-hadoop.html As we expected in the previous post, the activities of Apache Hadoop

Re: Looking to a Hadoop 3 release

2015-03-03 Thread Akira AJISAKA
Thanks Andrew for bringing this up. +1 mostly looks fine but I'm thinking it's not now to cut branch-3. > classpath isolation IMHO, classpath isolation is a good thing to do. We should pay down the technical dept ASAP. I'm willing to help. I'm thinking we can cut branch-3 and release 3.0 alpha

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

2015-03-03 Thread Apache Jenkins Server
See

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

2015-03-03 Thread Apache Jenkins Server
See Changes: [gera] HDFS-7789. DFSck should resolve the path to support cross-FS symlinks. (gera) [aajisaka] HADOOP-11658. Externalize io.compression.codecs property. Contributed by Kai Zheng. [jianhe] YARN-3281. Added RMStateSt

[jira] [Created] (HADOOP-11665) Provide and unify cross platform byteorder support in native code

2015-03-03 Thread Binglin Chang (JIRA)
Binglin Chang created HADOOP-11665: -- Summary: Provide and unify cross platform byteorder support in native code Key: HADOOP-11665 URL: https://issues.apache.org/jira/browse/HADOOP-11665 Project: Hado