[jira] [Created] (HDFS-8263) Erasure Coding: Test of fsck for EC files

GAO Rui created HDFS-8263: - Summary: Erasure Coding: Test of fsck for EC files Key: HDFS-8263 URL: https://issues.apache.org/jira/browse/HDFS-8263 Project: Hadoop HDFS Issue Type: Test Affects

[jira] [Created] (HDFS-8266) Erasure Coding: Test of snapshot/.trash with EC files

GAO Rui created HDFS-8266: - Summary: Erasure Coding: Test of snapshot/.trash with EC files Key: HDFS-8266 URL: https://issues.apache.org/jira/browse/HDFS-8266 Project: Hadoop HDFS Issue Type: Test

[jira] [Created] (HDFS-8271) NameNode should bind on both IPv6 and IPv4 if running on dual-stack machine and IPv6 enabled

Nate Edel created HDFS-8271: --- Summary: NameNode should bind on both IPv6 and IPv4 if running on dual-stack machine and IPv6 enabled Key: HDFS-8271 URL: https://issues.apache.org/jira/browse/HDFS-8271

[jira] [Created] (HDFS-8265) Erasure Coding: Test of Quota calculation for EC files

GAO Rui created HDFS-8265: - Summary: Erasure Coding: Test of Quota calculation for EC files Key: HDFS-8265 URL: https://issues.apache.org/jira/browse/HDFS-8265 Project: Hadoop HDFS Issue Type: Test

[jira] [Created] (HDFS-8262) Erasure Coding: Test of datanode decommission which EC blocks are stored

GAO Rui created HDFS-8262: - Summary: Erasure Coding: Test of datanode decommission which EC blocks are stored Key: HDFS-8262 URL: https://issues.apache.org/jira/browse/HDFS-8262 Project: Hadoop HDFS

[jira] [Created] (HDFS-8264) Erasure Coding: Test of version update

GAO Rui created HDFS-8264: - Summary: Erasure Coding: Test of version update Key: HDFS-8264 URL: https://issues.apache.org/jira/browse/HDFS-8264 Project: Hadoop HDFS Issue Type: Test Affects

[jira] [Created] (HDFS-8267) Erasure Coding: Test of Namenode with EC files

GAO Rui created HDFS-8267: - Summary: Erasure Coding: Test of Namenode with EC files Key: HDFS-8267 URL: https://issues.apache.org/jira/browse/HDFS-8267 Project: Hadoop HDFS Issue Type: Test

Build failed in Jenkins: Hadoop-Hdfs-trunk-Java8 #167

See https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/167/changes Changes: [kasha] YARN-3464. Race condition in LocalizerRunner kills localizer before localizing all resources. (Zhihai Xu via kasha) [aw] HADOOP-11865. Incorrect path mentioned in document for accessing script files

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

See https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/167/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 5182 lines...] [INFO] Executed tasks [INFO] [INFO]

[jira] [Created] (HDFS-8268) Port conflict log for data node server is not sufficient

Mohammad Shahid Khan created HDFS-8268: -- Summary: Port conflict log for data node server is not sufficient Key: HDFS-8268 URL: https://issues.apache.org/jira/browse/HDFS-8268 Project: Hadoop HDFS

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

See https://builds.apache.org/job/Hadoop-Hdfs-trunk/2108/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 5181 lines...] [INFO] Executed tasks [INFO] [INFO] ---

Build failed in Jenkins: Hadoop-Hdfs-trunk #2108

See https://builds.apache.org/job/Hadoop-Hdfs-trunk/2108/changes Changes: [kasha] YARN-3464. Race condition in LocalizerRunner kills localizer before localizing all resources. (Zhihai Xu via kasha) [aw] HADOOP-11865. Incorrect path mentioned in document for accessing script files (J.Andreina

[jira] [Created] (HDFS-8273) logSync() is called inside of write lock for delete op

Jing Zhao created HDFS-8273: --- Summary: logSync() is called inside of write lock for delete op Key: HDFS-8273 URL: https://issues.apache.org/jira/browse/HDFS-8273 Project: Hadoop HDFS Issue Type:

[jira] [Created] (HDFS-8272) Erasure Coding: simplify the retry logic in DFSStripedInputStream

Jing Zhao created HDFS-8272: --- Summary: Erasure Coding: simplify the retry logic in DFSStripedInputStream Key: HDFS-8272 URL: https://issues.apache.org/jira/browse/HDFS-8272 Project: Hadoop HDFS

Re: [DISCUSS] Release numbering for stable 2.8 and beyond

I think Karthik correctly identified the two reasons we might want to denote a release as unstable: a) Compatibility. Whether we have freedom to break compatibility before the final release, i.e. what alpha typically means. b) Quality. As Konst says, a release can be allowed to break

[jira] [Created] (HDFS-8270) create() always retried with hardcoded timeout.

Andrey Stepachev created HDFS-8270: -- Summary: create() always retried with hardcoded timeout. Key: HDFS-8270 URL: https://issues.apache.org/jira/browse/HDFS-8270 Project: Hadoop HDFS Issue

Planning Hadoop 2.6.1 release

There were several requests on the user lists [1] for a 2.6.1 release. I got many offline comments too. Planning to do a 2.6.1 release in a few weeks time. We already have a bunch of tickets committed to 2.7.1. I created a filter [2] to tracking pending tickets. We need to collectively come up

Re: HDFS audit log

Hi Allen, thanks for bringing this up. Two comments: - Is there a specification for the audit log format? i.e. is it something structured like JSON? I think I asked you this in-person, and you said it's something custom. I doubt that we can just freeze the format. In recent times we've added

[jira] [Created] (HDFS-8269) getBlockLocations() does not resolve the .reserved path and generates incorrect edit logs when updating the atime

Haohui Mai created HDFS-8269: Summary: getBlockLocations() does not resolve the .reserved path and generates incorrect edit logs when updating the atime Key: HDFS-8269 URL: