Re: LinkedIn Dynamometer Tool (was About 2.7.4 Release)

Erik Great stuff. BTW did you build on top of the “simulated data nodes” in HDFS which has a way to storing only the length of data (but not real data)? That work allowed supplementing with a matching editsLog for the NN. Your approach of using a real image has the advantage of being able

[jira] [Created] (HADOOP-14675) Path object disallows access to S3 objects with // in their names

Andi created HADOOP-14675: - Summary: Path object disallows access to S3 objects with // in their names Key: HADOOP-14675 URL: https://issues.apache.org/jira/browse/HADOOP-14675 Project: Hadoop Common

Re: Apache Hadoop 2.8.2 Release Plan

Thanks for suggestions, Jason and Kihwal! +1 on releasing 2.8.2 on latest branch-2.8 too. Practically, if branch-2.8.2 cannot be abandoned/replaced (suspect all branches are read-only now), I will manually merge all commits that not landed on 2.8.2 yet. Thanks, Junping

Re: Apache Hadoop 2.8.2 Release Plan

Junping, If we are looking at a month, I’d not rebranch branch-2.8.2 right now given how these things go. We can just continue to commit on branch-2.8 for now. I also think we should just follow up with ASF INFRA and clean up the branches - Delete branch-2.8.2 so that we can recreate it afresh

Re: Apache Hadoop 2.8.2 Release Plan

Make sense, just raise: https://issues.apache.org/jira/browse/INFRA-14669 Thanks, Junping From: Vinod Kumar Vavilapalli Sent: Friday, July 21, 2017 12:31 PM To: Junping Du Cc: Kihwal Lee; common-dev@hadoop.apache.org;

Re: LinkedIn Dynamometer Tool (was About 2.7.4 Release)

Hi Sanjay, Actually I was not aware of that work… This seems to be a better way of achieving some of the same things we do externally to the DN process. I will look into reimplementing some parts on top of this; seems it should just require some very small extensions to DataNodeCluster. Thank

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

For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/471/ [Jul 20, 2017 8:15:46 AM] (haibochen) YARN-6685. Add job count in to SLS JSON input format. (Yufei Gu via [Jul 20, 2017 9:03:04 AM] (jlowe) YARN-6837. Null LocalResource visibility or resource type can

[jira] [Created] (HADOOP-14674) Correct javadoc for getRandomizedTempPath

Mukul Kumar Singh created HADOOP-14674: -- Summary: Correct javadoc for getRandomizedTempPath Key: HADOOP-14674 URL: https://issues.apache.org/jira/browse/HADOOP-14674 Project: Hadoop Common

Re: Apache Hadoop 2.8.2 Release Plan

Thanks for driving the next 2.8 release, Junping. While I was committing a blocker for 2.7.4, I noticed some of the jiras are back-ported to 2.7, but missing in branch-2.8.2.  Perhaps it is safer and easier to simply rebranch 2.8.2. Thanks,Kihwal On Thursday, July 20, 2017, 3:32:16 PM CDT,

Re: Pre-Commit build is failing

What stuff? Is there a jira? It did work like a week ago. Is it a new Yetus requirement. Anyways I can commit a change to fix the build on our side. Just need to know what is missing. Thanks, --Konst On Fri, Jul 21, 2017 at 5:50 PM, Allen Wittenauer wrote: > > > On

[jira] [Created] (HADOOP-14676) Wrong default value for "fs.du.interval"

Konstantin Shvachko created HADOOP-14676: Summary: Wrong default value for "fs.du.interval" Key: HADOOP-14676 URL: https://issues.apache.org/jira/browse/HADOOP-14676 Project: Hadoop Common

Re: Pre-Commit build is failing

+ d...@yetus.apache.org Guys, could you please take a look. Seems like Yetus problem with pre-commit build for branch-2.7. Thanks, --Konstantin On Thu, Jul 20, 2017 at 7:19 PM, Brahma Reddy Battula < brahmareddy.batt...@huawei.com> wrote: > Looks this problem is in only branc-2.7.. > > >

Re: Apache Hadoop 2.8.2 Release Plan

Already get back from Daniel who is from ASF INFRA team, I plan to do following operations on next Monday morning: 1. Drop current branch-2.8.2 and recut branch-2.8.2 from branch-2.8 2. Drop abandoned branch-2.8.1 and rename branch-2.8.1-private to branch-2.8.1 where we just released 2.8.1 from.

Re: Apache Hadoop 2.8.2 Release Plan

+1 to base the 2.8.2 release off of the more recent activity on branch-2.8.  Because branch-2.8.2 was cut so long ago it is missing a lot of fixes that are in branch-2.8.  There also are a lot of JIRAs that claim they are fixed in 2.8.2 but are not in branch-2.8.2.  Having the 2.8.2 release be