[jira] [Resolved] (HDFS-8231) StackTrace displayed at client while QuotaByStorageType exceeds

[ https://issues.apache.org/jira/browse/HDFS-8231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinayakumar B resolved HDFS-8231. - Resolution: Fixed Fix Version/s: 2.8.0 Hadoop Flags: Reviewed > StackTrace displayed at

[jira] [Created] (HDFS-8240) Summary: During hdfs client is writing small file, missing block showed in namenode web when ha switch

Ricky Yang created HDFS-8240: Summary: Summary: During hdfs client is writing small file, missing block showed in namenode web when ha switch Key: HDFS-8240 URL: https://issues.apache.org/jira/browse/HDFS-8240

Re: fsck output compatibility question with regard to HDFS-7281

On Apr 24, 2015, at 5:53 AM, Yongjun Zhang wrote: > > Basically we are adding two additional lines to the report (as highlighted > above). > > Theoretically if a tool parses existing fsck report and expects the > 'Corrupt blocks" entry to be right after the "Average block replication" > entry,

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

See https://builds.apache.org/job/Hadoop-Hdfs-trunk/2105/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 5190 lines...] [INFO] Skipping javadoc generation [INFO]

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

See Changes: [tgraves] YARN-3434. Interaction between reservations and userlimit can result in significant ULF violation [arp] HADOOP-10597. RPC Server signals backoff to clients when all request queues are full. (Contributed by Mi

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

See https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/164/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 5193 lines...] [INFO] Not executing Javadoc as the p

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

See Changes: [tgraves] YARN-3434. Interaction between reservations and userlimit can result in significant ULF violation [arp] HADOOP-10597. RPC Server signals backoff to clients when all request queues are full. (Contributed

[jira] [Created] (HDFS-8241) Remove unused Namenode startup option "FINALIZE"

Brahma Reddy Battula created HDFS-8241: -- Summary: Remove unused Namenode startup option "FINALIZE" Key: HDFS-8241 URL: https://issues.apache.org/jira/browse/HDFS-8241 Project: Hadoop HDFS

[jira] [Created] (HDFS-8242) Erasure Coding: XML based end-to-end test for ECCli commands

Rakesh R created HDFS-8242: -- Summary: Erasure Coding: XML based end-to-end test for ECCli commands Key: HDFS-8242 URL: https://issues.apache.org/jira/browse/HDFS-8242 Project: Hadoop HDFS Issue Typ

[jira] [Created] (HDFS-8243) Files written by TestHostsFiles and TestNameNodeMXBean are causing Release Audit Warnings.

Ruth Wisniewski created HDFS-8243: - Summary: Files written by TestHostsFiles and TestNameNodeMXBean are causing Release Audit Warnings. Key: HDFS-8243 URL: https://issues.apache.org/jira/browse/HDFS-8243

[jira] [Created] (HDFS-8244) HDFS Custom Storage Tier Policies

Hari Sekhon created HDFS-8244: - Summary: HDFS Custom Storage Tier Policies Key: HDFS-8244 URL: https://issues.apache.org/jira/browse/HDFS-8244 Project: Hadoop HDFS Issue Type: New Feature

[jira] [Resolved] (HDFS-8228) Erasure Coding: SequentialBlockGroupIdGenerator#nextValue may cause block id conflicts

[ https://issues.apache.org/jira/browse/HDFS-8228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe Zhang resolved HDFS-8228. - Resolution: Fixed Assignee: Jing Zhao (was: Zhe Zhang) Hadoop Flags: Reviewed > Erasure Codi

Re: fsck output compatibility question with regard to HDFS-7281

Allen, thank you for calling this out. I was not aware of this part of the compatibility guidelines. I committed one of those fsck changes in HDFS-7933. I see you flagged the issue as incompatible, which agrees with the compatibility guidelines. "Changing the path of a command, removing or rena

Re: fsck output compatibility question with regard to HDFS-7281

Thanks Allen and Chris! What about adding new entries to jmx report? Somehow I had the impression that if we add new entries to it, it's not considered incompatible. Often within the same minor release, we want to add new info to jmx report instead of waiting for a major release. For CLI like fsc

[jira] [Created] (HDFS-8245) Standby namenode doesn't process DELETED_BLOCK if the add block request is in edit log.

Rushabh S Shah created HDFS-8245: Summary: Standby namenode doesn't process DELETED_BLOCK if the add block request is in edit log. Key: HDFS-8245 URL: https://issues.apache.org/jira/browse/HDFS-8245 P

Re: fsck output compatibility question with regard to HDFS-7281

Metrics/JMX is covered by our compatibility guidelines: http://hadoop.apache.org/docs/r2.7.0/hadoop-project-dist/hadoop-common/Comp atibility.html#MetricsJMX Metrics/JMX is similar to our usage of Protocol Buffers/JSON that I mentioned. It supports backwards-compatible evolution if the change i

Re: fsck output compatibility question with regard to HDFS-7281

Thanks Chris, good clarification! --Yongjun On Fri, Apr 24, 2015 at 12:36 PM, Chris Nauroth wrote: > Metrics/JMX is covered by our compatibility guidelines: > > http://hadoop.apache.org/docs/r2.7.0/hadoop-project-dist/hadoop-common/Comp > atibility.html#MetricsJMX > > > Metrics/JMX is similar t

[jira] [Created] (HDFS-8246) Get HDFS file name based on block pool id and block id

feng xu created HDFS-8246: - Summary: Get HDFS file name based on block pool id and block id Key: HDFS-8246 URL: https://issues.apache.org/jira/browse/HDFS-8246 Project: Hadoop HDFS Issue Type: New Fe

[jira] [Created] (HDFS-8247) TestDiskspaceQuotaUpdate is failing

Anu Engineer created HDFS-8247: -- Summary: TestDiskspaceQuotaUpdate is failing Key: HDFS-8247 URL: https://issues.apache.org/jira/browse/HDFS-8247 Project: Hadoop HDFS Issue Type: Bug C

[jira] [Created] (HDFS-8248) Store INodeId instead of the INodeFile object in BlockInfoContiguous

Haohui Mai created HDFS-8248: Summary: Store INodeId instead of the INodeFile object in BlockInfoContiguous Key: HDFS-8248 URL: https://issues.apache.org/jira/browse/HDFS-8248 Project: Hadoop HDFS

[jira] [Created] (HDFS-8249) Separate HdfsConstants into the client and the server side class

Haohui Mai created HDFS-8249: Summary: Separate HdfsConstants into the client and the server side class Key: HDFS-8249 URL: https://issues.apache.org/jira/browse/HDFS-8249 Project: Hadoop HDFS I

[jira] [Resolved] (HDFS-8033) Erasure coding: stateful (non-positional) read from files in striped layout

[ https://issues.apache.org/jira/browse/HDFS-8033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe Zhang resolved HDFS-8033. - Resolution: Fixed Fix Version/s: HDFS-7285 Hadoop Flags: Reviewed > Erasure coding: stateful (n