hedged read bug

I use hadoop2.4. When I use "hedged read", If there is only one live datanode, the reading from the datanode throw TimeoutException and ChecksumException., the Client will infinite wait. Example below test case: @Test public void testException() throws IOException, InterruptedException, Exec

[jira] [Resolved] (HDFS-6386) HDFS Encryption Zones

[ https://issues.apache.org/jira/browse/HDFS-6386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles Lamb resolved HDFS-6386. Resolution: Fixed Fix Version/s: fs-encryption (HADOOP-10150 and HDFS-6134) committed > HDFS

[jira] [Resolved] (HDFS-6473) Protocol and API for Encryption Zones

[ https://issues.apache.org/jira/browse/HDFS-6473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles Lamb resolved HDFS-6473. Resolution: Fixed Fix Version/s: fs-encryption (HADOOP-10150 and HDFS-6134) > Protocol and AP

[jira] [Reopened] (HDFS-6386) HDFS Encryption Zones

[ https://issues.apache.org/jira/browse/HDFS-6386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles Lamb reopened HDFS-6386: sorry, resolved the wrong jira > HDFS Encryption Zones > - > > Key:

[jira] [Resolved] (HDFS-2064) Warm HA NameNode going Hot

[ https://issues.apache.org/jira/browse/HDFS-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko resolved HDFS-2064. --- Resolution: Won't Fix Closing this in favor of HDFS-6469. > Warm HA NameNode going Ho

[jira] [Created] (HDFS-6493) Propose to change "dfs.namenode.startup.delay.block.deletion" to second instead of millisecond

Juan Yu created HDFS-6493: - Summary: Propose to change "dfs.namenode.startup.delay.block.deletion" to second instead of millisecond Key: HDFS-6493 URL: https://issues.apache.org/jira/browse/HDFS-6493 Project:

[jira] [Created] (HDFS-6492) Support create-time xattrs and atomically setting multiple xattrs

Andrew Wang created HDFS-6492: - Summary: Support create-time xattrs and atomically setting multiple xattrs Key: HDFS-6492 URL: https://issues.apache.org/jira/browse/HDFS-6492 Project: Hadoop HDFS

[jira] [Created] (HDFS-6491) proposal for developing a tool to compare files/dirs

Yongjun Zhang created HDFS-6491: --- Summary: proposal for developing a tool to compare files/dirs Key: HDFS-6491 URL: https://issues.apache.org/jira/browse/HDFS-6491 Project: Hadoop HDFS Issue Ty

[jira] [Created] (HDFS-6490) Fix the keyid format for generated keys in FSNamesystem.createEncryptionZone

Charles Lamb created HDFS-6490: -- Summary: Fix the keyid format for generated keys in FSNamesystem.createEncryptionZone Key: HDFS-6490 URL: https://issues.apache.org/jira/browse/HDFS-6490 Project: Hadoop

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

See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1765/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 15157 lines...] [INFO] [INFO] --- maven-antrun-plugin:1.

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

See Changes: [kasha] YARN-2061. Revisit logging levels in ZKRMStateStore. (Ray Chiang via kasha) [kasha] YARN-2119. DEFAULT_PROXY_ADDRESS should use DEFAULT_PROXY_PORT. (Anubhav Dhoot via kasha) ---

[jira] [Resolved] (HDFS-6392) Wire crypto streams for encrypted files in DFSClient

[ https://issues.apache.org/jira/browse/HDFS-6392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles Lamb resolved HDFS-6392. Resolution: Fixed Fix Version/s: fs-encryption (HADOOP-10150 and HDFS-6134) Target V

[jira] [Created] (HDFS-6489) DFS Used space is not correct if there're many append operations

stanley shi created HDFS-6489: - Summary: DFS Used space is not correct if there're many append operations Key: HDFS-6489 URL: https://issues.apache.org/jira/browse/HDFS-6489 Project: Hadoop HDFS