[jira] [Created] (HADOOP-15121) Encounter NullPointerException when using DecayRpcScheduler

Tao Jie created HADOOP-15121: Summary: Encounter NullPointerException when using DecayRpcScheduler Key: HADOOP-15121 URL: https://issues.apache.org/jira/browse/HADOOP-15121 Project: Hadoop Common

Re: Missing some trunk commit history

Hi Chris, I am looking for a way to reduce time spent on testing latest commits. When trunk broke, it is usually someone didn't do a full build to test the patch. If a feature merge results in 100+ commit additions. It is difficult to tell where breakage occurred. A single merge point is

Re: [ANNOUNCE] Apache Hadoop 3.0.0 GA is released

Hi Andrew Congratulations on the 3.0 GA, another mile stone of Hadoop history. Thanks for driving this release, excellent work! Took a look at the release notes, also seems nice. But one question, who is maintaining https://wiki.apache.org/hadoop/PoweredBy? Some of info is quite out of date,

Re: Missing some trunk commit history

Eric- What problem are you trying to solve? Most of us understand how git works, you can omit that. -C On Thu, Dec 14, 2017 at 6:31 PM Eric Yang wrote: > We are currently requesting committer to commit code base on: > https://wiki.apache.org/hadoop/HowToCommit > > To set

Re: Missing some trunk commit history

We are currently requesting committer to commit code base on: https://wiki.apache.org/hadoop/HowToCommit To set branch.autosetuprebase always: Base on the current preference, the history is linear, and it is described in this graph as Rebase and Merge:

[jira] [Created] (HADOOP-15120) AzureNativeFileSystemStore

Yin Huai created HADOOP-15120: - Summary: AzureNativeFileSystemStore Key: HADOOP-15120 URL: https://issues.apache.org/jira/browse/HADOOP-15120 Project: Hadoop Common Issue Type: Bug

[jira] [Created] (HADOOP-15119) AzureNativeFileSystemStore's rename swallow InterruptedExceptions

Yin Huai created HADOOP-15119: - Summary: AzureNativeFileSystemStore's rename swallow InterruptedExceptions Key: HADOOP-15119 URL: https://issues.apache.org/jira/browse/HADOOP-15119 Project: Hadoop Common

Re: Missing some trunk commit history

I'm sorry, I literally don't understand what you've written. What do clicks on github have to do with merges? Are you talking about git bisect, where one would first identify the branch where the error was introduced, then run a second regression over the feature branch? With similar semantics

Re: Missing some trunk commit history

When details are rebased, the number of entries to test through the linear history is much more than a merge point to isolate where the error might have occurred. It is similar to traverse a tree structure, for each branch, there are n branches to walk through. If we can know where the

Re: Missing some trunk commit history

I'd rather have the history. Otherwise tools like blame point only to a parent/umbrella JIRA, not the issue where the change was discussed. We can force a merge commit so it's clear the branch was developed outside the mainline. -C On Thu, Dec 14, 2017 at 1:18 PM, Eric Yang

Re: Missing some trunk commit history

+1 on squash merge to keep history compressed. The rebase + merge contains good deals, but it is easy to get confused for people that doesn’t know about the rebase option is turned on by default for Hadoop. Regards, Eric On 12/14/17, 12:06 PM, "Arun Suresh" wrote:

Re: [VOTE] Release Apache Hadoop 2.7.5 (RC1)

Great work Konstantin. +1 (binding) - Downloaded both source and binary tar files and verified checksums - Deployed pseudo-distributed cluster and verified basic HDFS operations (mkdir, copyFromLocal) - Verified both NameNode and RM UIs On Wed, Dec 13, 2017 at 12:05 PM Jonathan Hung

Re: Missing some trunk commit history

Another option - atleast for feature branches is to maybe squash merge - this way we see it as a single commit ? Although we will loose the feature branch history (I am ok with that though) Cheers -Arun On Thu, Dec 14, 2017 at 11:32 AM, Eric Yang wrote: > Thank you for

Re: Missing some trunk commit history

Thank you for the pointer. I guess all merge are done using rebase + merge. This is the reason that timeline is out of order. Would it be more useful to merge without rebasing for feature branch merge to avoid timeline confusions? The argument for not rebasing, it would be easier to find

Re: Missing some trunk commit history

Hi Eric. A branch merge has happened during that time, and hence you might have seen some old commits from that branch. If you go down further, you could see those commits. Copied from my git log: commit 40b0045ebe0752cd3d1d09be00acbabdea983799 Author: Weiwei Yang Date: Wed

Missing some trunk commit history

Hi all, While troubleshooting a trunk build failure, I notice the commit history for trunk between Nov 30th to Dec 6th are squashed or disappeared for no reason. This seems to have taken place in the last 24 hours. I can see the commit logs from github UI. When doing a new clone from Apache

[ANNOUNCE] Apache Hadoop 3.0.0 GA is released

Hi all, I'm pleased to announce that Apache Hadoop 3.0.0 is generally available (GA). 3.0.0 GA consists of 302 bug fixes, improvements, and other enhancements since 3.0.0-beta1. This release marks a point of quality and stability for the 3.0.0 release line, and users of earlier 3.0.0-alpha and

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

For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/622/ [Dec 13, 2017 5:19:58 PM] (sunilg) YARN-7643. Handle recovery of applications in case of auto-created leaf [Dec 13, 2017 9:05:32 PM] (wang) Update CHANGES, RELEASENOTES, jdiff for 3.0.0 release. [Dec 13,