Re: [DISCUSS] The order of classpath isolation work and updating/shading dependencies on trunk

> On Jul 22, 2016, at 5:47 PM, Zheng, Kai wrote: > > For the leveldb thing, wouldn't we have an alternative option in Java for the > platforms where leveldb isn't supported yet due to whatever reasons. IMO, > native library would be best to be used for optimization and

Re: Setting JIRA fix versions for 3.0.0 releases

> On Jul 22, 2016, at 7:16 PM, Andrew Wang wrote: > > Does this mean you find our current system of listing a JIRA as being fixed > in both a 2.6.x and 2.7.x to be confusing? Nope. I'm only confused when there isn't a .0 release in the fix line. When I see

Re: Setting JIRA fix versions for 3.0.0 releases

Thanks for the input Allen, good perspective as always, inline: > From the perspective of an end user who is reading multiple > versions' listings at once, listing the same JIRA being fixed in multiple > releases is totally confusing, especially now that release notes are > actually

[VOTE] Release Apache Hadoop 2.7.3 RC0

Hi all, I've created a release candidate RC0 for Apache Hadoop 2.7.3. As discussed before, this is the next maintenance release to follow up 2.7.2. The RC is available for validation at: http://home.apache.org/~vinodkv/hadoop-2.7.3-RC0/ The

RE: [DISCUSS] The order of classpath isolation work and updating/shading dependencies on trunk

For the leveldb thing, wouldn't we have an alternative option in Java for the platforms where leveldb isn't supported yet due to whatever reasons. IMO, native library would be best to be used for optimization and production for performance. For development and pure Java platform, by default

Re: [DISCUSS] The order of classpath isolation work and updating/shading dependencies on trunk

But if I don't use ApplicationClassLoader, my java app is basically screwed then, right? Also: right now, the non-Linux and/or non-x86 platforms have to supply their own leveldbjni jar (or at least the C level library?) in order to make YARN even functional. How is that going to work with

Re: [DISCUSS] 2.6.x line releases

Thanks for pointing it out Allen. I'll work on an addendum 2.6 patch for HADOOP-12800. On Fri, Jul 22, 2016 at 3:59 PM Allen Wittenauer wrote: > > > On Jul 22, 2016, at 9:07 AM, Zhe Zhang > wrote: > > > > Thanks Allen for the note. I

Re: [DISCUSS] 2.6.x line releases

> On Jul 22, 2016, at 9:07 AM, Zhe Zhang wrote: > > Thanks Allen for the note. I thought the 2.6 Dockerfile issue was addressed > in https://issues.apache.org/jira/browse/HADOOP-12800? 2.6 builds on JDK6 and JDK7. 2.x, where x>6, builds on JDK7 and JDK8. [1]

Re: Setting JIRA fix versions for 3.0.0 releases

From the perspective of an end user who is reading multiple versions' listings at once, listing the same JIRA being fixed in multiple releases is totally confusing, especially now that release notes are actually readable. "So which version was it ACTUALLY fixed in?" is going to be the

Re: 2.7.3 release plan

The nexus issue persists to date. I have been constantly getting “Remote end closed due to a SSH handshake” issue. Tried to upload the artifacts in piece, but that was too slow, spanned across days. Finally found a “ DretryFailedDeploymentCount=10” option to mvn-deploy. Sending out the vote

[jira] [Created] (HADOOP-13409) Andrew's test JIRA

Andrew Wang created HADOOP-13409: Summary: Andrew's test JIRA Key: HADOOP-13409 URL: https://issues.apache.org/jira/browse/HADOOP-13409 Project: Hadoop Common Issue Type: Bug

Re: Setting JIRA fix versions for 3.0.0 releases

> > >> I am also not quite sure I understand the rationale of what's in the > HowToCommit wiki. Assuming the semantic versioning (http://semver.org) as > our baseline thinking, having concurrent release streams alone breaks the > principle. And that is *regardless of* how we line up individual

Re: Setting JIRA fix versions for 3.0.0 releases

On Thu, Jul 21, 2016 at 3:58 PM, Andrew Wang wrote: > Thanks for the input Vinod, inline: > > > > Similarly the list of features we are enabling in this alpha would be > good > > - may be update the Roadmap wiki. Things like classpath-isolation which > > were part of

Re: [DISCUSS] The order of classpath isolation work and updating/shading dependencies on trunk

The work on HADOOP-13070 and the ApplicationClassLoader are generic and go beyond YARN. It can be used in any JVM that uses hadoop. The current use cases are MR containers, hadoop's RunJar (as in "hadoop jar"), and the YARN node manager auxiliary services. I'm not sure if that's what you were

Re: [DISCUSS] The order of classpath isolation work and updating/shading dependencies on trunk

My work on HADOOP-11804 *only* helps processes that sit outside of YARN. :) On Fri, Jul 22, 2016 at 10:48 AM, Allen Wittenauer wrote: > > Does any of this work actually help processes that sit outside of YARN? > >> On Jul 21, 2016, at 12:29 PM, Sean Busbey

Re: [DISCUSS] 2.6.x line releases

Thanks Allen for the note. I thought the 2.6 Dockerfile issue was addressed in https://issues.apache.org/jira/browse/HADOOP-12800? On Fri, Jul 22, 2016 at 9:04 AM Allen Wittenauer wrote: > > > On Jul 21, 2016, at 5:06 PM, Zhe Zhang >

Re: [DISCUSS] 2.6.x line releases

> On Jul 21, 2016, at 5:06 PM, Zhe Zhang wrote: > > We are using 2.6 releases and would like to see 2.6.5. > > One related issue, pre-commit is not working for 2.6 (see comment from > Allen >

Re: [DISCUSS] The order of classpath isolation work and updating/shading dependencies on trunk

Does any of this work actually help processes that sit outside of YARN? > On Jul 21, 2016, at 12:29 PM, Sean Busbey wrote: > > thanks for bringing this up! big +1 on upgrading dependencies for 3.0. > > I have an updated patch for HADOOP-11804 ready to post this week. I've

Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86

For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/110/ [Jul 21, 2016 11:41:02 PM] (xiao) HDFS-10225. DataNode hot swap drives should disallow storage type [Jul 22, 2016 6:21:47 AM] (cdouglas) HADOOP-13393. Omit unsupported fs.defaultFS setting in ADLS -1

[jira] [Created] (HADOOP-13407) s3a directory housekeeping operations to be done in async thread

Steve Loughran created HADOOP-13407: --- Summary: s3a directory housekeeping operations to be done in async thread Key: HADOOP-13407 URL: https://issues.apache.org/jira/browse/HADOOP-13407 Project:

Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86

For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/109/ No changes -1 overall The following subsystems voted -1: asflicense unit The following subsystems voted -1 but were configured to be filtered/ignored: cc checkstyle javac javadoc pylint

[jira] [Created] (HADOOP-13406) S3AFileSystem: Consider reusing filestatus in delete and mkdir

Rajesh Balamohan created HADOOP-13406: - Summary: S3AFileSystem: Consider reusing filestatus in delete and mkdir Key: HADOOP-13406 URL: https://issues.apache.org/jira/browse/HADOOP-13406 Project: