[jira] [Resolved] (HDFS-8684) Erasure Coding: fix some block number calculation for striped block

2015-07-06 Thread Yi Liu (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-8684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Liu resolved HDFS-8684. -- Resolution: Fixed Hadoop Flags: Reviewed Thanks Vinay and Walter for review, committed to the branch. > Er

Hadoop-Hdfs-trunk - Build # 2175 - Still Failing

2015-07-06 Thread Apache Jenkins Server
See https://builds.apache.org/job/Hadoop-Hdfs-trunk/2175/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 7362 lines...] [INFO] [INFO] --- maven-source-plugin:2.3

Hadoop-Hdfs-trunk-Java8 - Build # 236 - Still Failing

2015-07-06 Thread Apache Jenkins Server
See https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/236/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 7914 lines...] [INFO] [INFO] --- maven-source-plugi

[jira] [Created] (HDFS-8716) introduce a new config specifically for safe mode block count

2015-07-06 Thread Chang Li (JIRA)
Chang Li created HDFS-8716: -- Summary: introduce a new config specifically for safe mode block count Key: HDFS-8716 URL: https://issues.apache.org/jira/browse/HDFS-8716 Project: Hadoop HDFS Issue Ty

[RESULT][VOTE] Release Apache Hadoop 2.7.1 RC0

2015-07-06 Thread Vinod Kumar Vavilapalli
Here’s my +1 to end the vote. With 6 binding +1s, 12 non-binding +1s, this release-vote passes. Thanks everyone who voted! I’ll follow up on the post-voting release process. Thanks +Vinod > On Jun 29, 2015, at 1:45 AM, Vinod Kumar Vavilapalli > wrote: > > Hi all, > > I've created a releas

[jira] [Created] (HDFS-8717) OzoneHandler : Add common bucket objects

2015-07-06 Thread Anu Engineer (JIRA)
Anu Engineer created HDFS-8717: -- Summary: OzoneHandler : Add common bucket objects Key: HDFS-8717 URL: https://issues.apache.org/jira/browse/HDFS-8717 Project: Hadoop HDFS Issue Type: Sub-task

Re: NameNode as a single point of failure

2015-07-06 Thread Konstantin Shvachko
Hey Dmitry, You understood correctly that QJM with automatic failover is the current state of the art for HDFS. With it we still have a single active NameNode on the cluster at any given time, which does not solve the performance bottleneck problem. I think active-active HA would have been an impr

Re: NameNode as a single point of failure

2015-07-06 Thread Dmitry Salychev
Hi Konstantin, I can not reply to you about WANdisco's proprietary system right now, I'll have to talk to our team. I'm afraid that we are not ready for paid solution, I guess. Generally, I'm looking for an entry point to contribute to Hadoop or related projects (like HDFS, and so on). I think