[jira] [Resolved] (HADOOP-11334) Mapreduce Job Failed due to failure fetching mapper output on the reduce side

[ https://issues.apache.org/jira/browse/HADOOP-11334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuanbo Liu resolved HADOOP-11334. - Resolution: Implemented > Mapreduce Job Failed due to failure fetching mapper output on the redu

[jira] [Created] (HADOOP-13004) Not able to access AWS

Bhavan Jindal created HADOOP-13004: -- Summary: Not able to access AWS Key: HADOOP-13004 URL: https://issues.apache.org/jira/browse/HADOOP-13004 Project: Hadoop Common Issue Type: Bug

Jenkins build is back to normal : Hadoop-Common-trunk #2590

See

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

See Changes: [kihwal] HDFS-10261. TestBookKeeperHACheckpoints doesn't handle ephemeral HTTP -- [...truncated 3847 lines...] Generating

Re: 2.7.3 release plan

I'm +1 for ctrezzo's proposal, happy to do the revert from branch-2.7 if this is acceptable to Vinod. There's some additional discussion on the HDFS-8791 JIRA for those who are only following this email thread. Best, Andrew On Tue, Apr 5, 2016 at 2:03 PM, Chris Trezzo wrote: > In light of the

Re: 2.7.3 release plan

In light of the additional conversation on HDFS-8791, I would like to re-propose the following: 1. Revert the new datanode layout (HDFS-8791) from the 2.7 branch. The layout change currently does not support downgrades which breaks our upgrade/downgrade policies for dot releases. 2. Cut a 2.8 rel

Re: Github integration for Hadoop

Thanks, Vinayakumar (and Daniel Gruno.) C. On Tue, Apr 5, 2016, at 08:48, Vinayakumar B wrote: > INFRA-11597 has been fixed. Now all github mails are diverted to > common-iss...@hadoop.apache.org > > -Vinay > > On Tue, Apr 5, 2016 at 1:05 PM, Vinayakumar B > wrote: > > > https://issues.apache

Re: Github integration for Hadoop

INFRA-11597 has been fixed. Now all github mails are diverted to common-iss...@hadoop.apache.org -Vinay On Tue, Apr 5, 2016 at 1:05 PM, Vinayakumar B wrote: > https://issues.apache.org/jira/browse/INFRA-11597 has been filed for this. > > -Vinay > > -Original Message- > From: Colin McCab

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

See

Re: [Release thread] 2.8.0 release activities

> On 4 Apr 2016, at 22:16, Vinod Kumar Vavilapalli wrote: > > Here we go again. The blocker / critical tickets ballooned up a lot, I see 64 > now! : https://issues.apache.org/jira/issues/?filter=12334985 > > Also, the docs target (mvn package -Pdocs -DskipTests) is completely busted > on bran

Build failed in Jenkins: Hadoop-common-trunk-Java8 #1291

See Changes: [rohithsharmaks] YARN-4880. Running TestZKRMStateStorePerf with real zookeeper cluster [rohithsharmaks] YARN-4609. RM Nodes list page takes too much time to load. Contributed --

[jira] [Created] (HADOOP-13003) Add support for pushing metrics to OpenTSDB with Http

zhangyubiao created HADOOP-13003: Summary: Add support for pushing metrics to OpenTSDB with Http Key: HADOOP-13003 URL: https://issues.apache.org/jira/browse/HADOOP-13003 Project: Hadoop Common

Re: [Release thread] 2.8.0 release activities

> Also, the docs target (mvn package -Pdocs -DskipTests) is completely busted on branch-2, I figured I have to backport a whole bunch of patches that are only on trunk, and may be more fixes on top of that *sigh* To fix this failure, HADOOP-12022 should be backported to branch-2 and branch-2.8

[jira] [Reopened] (HADOOP-12022) fix site -Pdocs -Pdist in hadoop-project-dist; cleanout remaining forrest bits

[ https://issues.apache.org/jira/browse/HADOOP-12022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA reopened HADOOP-12022: This patch should be backported to branch-2 and branch-2.8. Reopening. > fix site -Pdocs -Pdi

RE: Github integration for Hadoop

https://issues.apache.org/jira/browse/INFRA-11597 has been filed for this. -Vinay -Original Message- From: Colin McCabe [mailto:co...@cmccabe.xyz] Sent: 05 April 2016 08:07 To: common-dev@hadoop.apache.org Subject: Re: Github integration for Hadoop Yes, please. Let's disable these mail