[jira] [Created] (HADOOP-15123) KDiag tries to load krb5.conf from KRB5CCNAME instead of KRB5_CONFIG

Vipin Rathor created HADOOP-15123: - Summary: KDiag tries to load krb5.conf from KRB5CCNAME instead of KRB5_CONFIG Key: HADOOP-15123 URL: https://issues.apache.org/jira/browse/HADOOP-15123 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/623/ [Dec 14, 2017 6:58:16 PM] (xyao) HADOOP-10054. ViewFsFileStatus.toString() is broken. Contributed by [Dec 14, 2017 8:58:47 PM] (kihwal) HDFS-12907. Allow read-only access to reserved raw for

Apache Hadoop qbt Report: branch2+JDK7 on Linux/x86

For more details, see https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/69/ [Dec 14, 2017 8:03:34 AM] (yqlin) HDFS-12883. RBF: Document Router and State Store metrics. Contributed by -1 overall The following subsystems voted -1: asflicense unit xml The following

[jira] [Created] (HADOOP-15122) Lock down version of doxia-module-markdown plugin

Elek, Marton created HADOOP-15122: - Summary: Lock down version of doxia-module-markdown plugin Key: HADOOP-15122 URL: https://issues.apache.org/jira/browse/HADOOP-15122 Project: Hadoop Common

Re: [ANNOUNCE] Apache Hadoop 3.0.0 GA is released

Hi Andrew, Thank you for all the hard work on this release. I was out the last few days and didn’t get a chance to evaluate RC1 earlier. The changelog looks incorrect. E.g. This gives an impression that there are just 5 incompatible changes in 3.0.0.

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

Sorry for the delayed reply, and thanks for the work Konstantin +1 Binding Verified the following: - Downloaded the tar on Ubuntu and verified the signatures - Deployed pseudo cluster - Sanity checks - Basic hdfs operations - Spark PyWordcount & few MR jobs (sleep , word count

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

Here is my formal +1. Thanks, --Konstantin On Thu, Dec 7, 2017 at 7:22 PM, Konstantin Shvachko wrote: > Hi everybody, > > I updated CHANGES.txt and fixed documentation links. > Also committed MAPREDUCE-6165, which fixes a consistently failing test. > > This is RC1 for

[RESULT] [VOTE] Release Apache Hadoop 2.7.5 (RC1)

Hi everybody, With 6 binding and 4 non-binding +1s and no -1s the vote for Apache Release 2.7.5 passes. Thank you everybody for contributing to the release, testing it, and voting. Binding +1s Kihwal Lee Jason Lowe John Zhuge Rohith Sharma K S Eric Payne Zhe Zhang Non-binding +1s Erik Krogen

[RESULT] [VOTE] Release Apache Hadoop 2.7.5 (RC1)

Correction: With 7 binding and 4 non-binding +1s and no -1s the vote for Apache Release 2.7.5 passes. Thank you everybody for contributing to the release, testing it, and voting. Binding +1s Kihwal Lee Jason Lowe John Zhuge Rohith Sharma K S Eric Payne Zhe Zhang Konstantin Shvachko Non-binding

Re: Missing some trunk commit history

On Thu, Dec 14, 2017 at 9:40 PM, Eric Yang wrote: > I am looking for a way to reduce time spent on testing latest commits. > [...] > People who did the > feature merge is likely already did the full build test to ensure they > didn't break trunk, but there is no easy indicator

Re: [ANNOUNCE] Apache Hadoop 3.0.0 GA is released

Hi Arpit, If you look at the release announcements, it's made clear that the changelog for 3.0.0 is diffed based on beta1. This is important since users need to know what's different from the previous 3.0.0-* releases if they're upgrading. I agree there's additional value to making combined

Re: Missing some trunk commit history

Eric, if you prefer to view commits in order of author date, you can use this one-liner courtesy of this site[1]: git log --pretty="format:%at commit %C(yellow)%H%Creset\nAuthor: %an <%ae>\nDate: %aD\n\n %s\n" | sort -r | cut -d" " -f2- | sed -e "s/\\\n/\\`echo -e '\n\r'`/g" | tr -d '\15\32' |

Re: Missing some trunk commit history

We actually already did: https://lists.apache.org/thread.html/43cd65c6b6c3c0e8ac2b3c76afd9eff1f78b177fabe9c4a96d9b3d0b@1440189889@%3Ccommon-dev.hadoop.apache.org%3E On Fri, Dec 15, 2017 at 10:54 AM, Eric Yang wrote: > +1 for merge –no-ff for feature merge. > Do we all

[RESULT] [VOTE] Release Apache Hadoop 2.7.5 (RC1)

Updating again to reflect all votes. Correction: With 8 binding and 4 non-binding +1s and no -1s the vote for Apache Release 2.7.5 passes. Thank you everybody for contributing to the release, testing it, and voting. Binding +1s Kihwal Lee Jason Lowe John Zhuge Rohith Sharma K S Eric Payne Zhe

Re: Missing some trunk commit history

+1 for merge –no-ff for feature merge. Do we all agree on this optimization for going forward? Regards, Eric On 12/15/17, 10:34 AM, "Chris Douglas" wrote: On Thu, Dec 14, 2017 at 9:40 PM, Eric Yang wrote: > I am looking for a way to reduce time

[jira] [Reopened] (HADOOP-15085) Output streams closed with IOUtils suppressing write errors

[ https://issues.apache.org/jira/browse/HADOOP-15085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan reopened HADOOP-15085: -- Reopening so I can put up a patch for branch-2. > Output streams closed with IOUtils suppressing

Hadoop 3.1.0 release discussion

Hi all, Congratulations on the 3.0.0-GA release! As we discussed in the previous email thread [1], I'd like to restart 3.1.0 release plans. a) Quick summary: a.1 Release status We started 3.1 release discussion on Sep 6, 2017 [1]. As of today, there’re 232 patches loaded on 3.1.0 alone [2],

Re: Missing some trunk commit history

Good catch on the history votes. It looks like we didn’t follow our own process because the voting thread wasn’t very clear about –no-ff vs –squash. I think –no-ff is the right solution to make sure the check point contains the delta of the merge to make sure the person who did the merge, did