[jira] [Created] (HDFS-10718) Prefer direct ByteBuffer in native RS encoder and decoder

SammiChen created HDFS-10718: Summary: Prefer direct ByteBuffer in native RS encoder and decoder Key: HDFS-10718 URL: https://issues.apache.org/jira/browse/HDFS-10718 Project: Hadoop HDFS Issue T

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

For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/122/ [Aug 2, 2016 8:07:59 AM] (aajisaka) HDFS-10707. Replace org.apache.commons.io.Charsets with [Aug 2, 2016 11:25:10 AM] (vvasudev) YARN-5443. Add support for docker inspect command. Contributed by Shane [Aug

[jira] [Created] (HDFS-10719) In HA, Namenode is failed to start If any of the Quorum hostname is unresolved.

Karthik Palanisamy created HDFS-10719: - Summary: In HA, Namenode is failed to start If any of the Quorum hostname is unresolved. Key: HDFS-10719 URL: https://issues.apache.org/jira/browse/HDFS-10719

[jira] [Created] (HDFS-10720) Fix intermittent test failure of TestDataNodeErasureCodingMetrics#testEcTasks

Rakesh R created HDFS-10720: --- Summary: Fix intermittent test failure of TestDataNodeErasureCodingMetrics#testEcTasks Key: HDFS-10720 URL: https://issues.apache.org/jira/browse/HDFS-10720 Project: Hadoop HDF

Re: [DISCUSS] Release numbering semantics with concurrent (>2) releases [Was Setting JIRA fix versions for 3.0.0 releases]

1. I probably missed something but I didn't get it how "alpha"s made their way into release numbers again. This was discussed on several occasions and I thought the common perception was to use just three level numbers for release versioning and avoid branding them. It is particularly confusing to