[jira] [Updated] (HDFS-2034) length in getBlockRange becomes -ve when reading only from currently being written blk

[ https://issues.apache.org/jira/browse/HDFS-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John George updated HDFS-2034: -- Status: Patch Available (was: Open) > length in getBlockRange becomes -ve when reading only from curren

[jira] [Updated] (HDFS-420) Fuse-dfs should cache fs handles

[ https://issues.apache.org/jira/browse/HDFS-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-420: - Resolution: Fixed Hadoop Flags: [Reviewed] Status: Resolved (was: Patch Available) I've co

[jira] [Created] (HDFS-2084) Sometimes backup node/secondary name node stops with exception

Sometimes backup node/secondary name node stops with exception -- Key: HDFS-2084 URL: https://issues.apache.org/jira/browse/HDFS-2084 Project: Hadoop HDFS Issue Type: Bug

[jira] [Updated] (HDFS-2084) Sometimes backup node/secondary name node stops with exception

[ https://issues.apache.org/jira/browse/HDFS-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Tymchyshyn updated HDFS-2084: - Tags: workaround Status: Patch Available (was: Open) This is my patch to skip such

[jira] [Updated] (HDFS-2084) Sometimes backup node/secondary name node stops with exception

[ https://issues.apache.org/jira/browse/HDFS-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Tymchyshyn updated HDFS-2084: - Attachment: patch.diff This is patch to skip such entries. Note that it's against my "own

[jira] [Commented] (HDFS-420) Fuse-dfs should cache fs handles

[ https://issues.apache.org/jira/browse/HDFS-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052042#comment-13052042 ] Hudson commented on HDFS-420: - Integrated in Hadoop-Hdfs-trunk-Commit #751 (See [https://builds

[jira] [Commented] (HDFS-1568) Improve DataXceiver error logging

[ https://issues.apache.org/jira/browse/HDFS-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052043#comment-13052043 ] Tsz Wo (Nicholas), SZE commented on HDFS-1568: -- The previous build failed unex

[jira] [Commented] (HDFS-2084) Sometimes backup node/secondary name node stops with exception

[ https://issues.apache.org/jira/browse/HDFS-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052048#comment-13052048 ] Hadoop QA commented on HDFS-2084: - -1 overall. Here are the results of testing the latest

[jira] [Commented] (HDFS-1568) Improve DataXceiver error logging

[ https://issues.apache.org/jira/browse/HDFS-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052079#comment-13052079 ] Joey Echeverria commented on HDFS-1568: --- Thanks. > Improve DataXceiver error logging

[jira] [Updated] (HDFS-1765) Block Replication should respect under-replication block priority

[ https://issues.apache.org/jira/browse/HDFS-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haryadi Gunawi updated HDFS-1765: - Attachment: underReplicatedQueue.pdf > Block Replication should respect under-replication block pr

[jira] [Commented] (HDFS-1765) Block Replication should respect under-replication block priority

[ https://issues.apache.org/jira/browse/HDFS-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052086#comment-13052086 ] Haryadi Gunawi commented on HDFS-1765: -- I agree with Hairong. Recently, I've been play

[jira] [Commented] (HDFS-2080) Speed up DFS read path

[ https://issues.apache.org/jira/browse/HDFS-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052090#comment-13052090 ] Kihwal Lee commented on HDFS-2080: -- This is awesome! I will review the patch carefully, bu

[jira] [Commented] (HDFS-2080) Speed up DFS read path

[ https://issues.apache.org/jira/browse/HDFS-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052119#comment-13052119 ] Todd Lipcon commented on HDFS-2080: --- bq. Did you compare the performance of "software" ve

[jira] [Created] (HDFS-2085) 1073: finalize inprogress edit logs at startup

1073: finalize inprogress edit logs at startup -- Key: HDFS-2085 URL: https://issues.apache.org/jira/browse/HDFS-2085 Project: Hadoop HDFS Issue Type: Sub-task Reporter: Todd Lipcon

[jira] [Updated] (HDFS-2085) 1073: finalize inprogress edit logs at startup

[ https://issues.apache.org/jira/browse/HDFS-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-2085: -- Description: With HDFS-2074, the NameNode can read through any "in-progress" logs it finds during startu

[jira] [Updated] (HDFS-2085) 1073: finalize inprogress edit logs at startup

[ https://issues.apache.org/jira/browse/HDFS-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-2085: -- Component/s: name-node Affects Version/s: Edit log branch (HDFS-1073) Fix Version/s: Ed

[jira] [Updated] (HDFS-2085) 1073: finalize inprogress edit logs at startup

[ https://issues.apache.org/jira/browse/HDFS-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-2085: -- Attachment: hdfs-2085.txt > 1073: finalize inprogress edit logs at startup > ---

[jira] [Commented] (HDFS-941) Datanode xceiver protocol should allow reuse of a connection

[ https://issues.apache.org/jira/browse/HDFS-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052160#comment-13052160 ] Konstantin Shvachko commented on HDFS-941: -- I ran some test myself over the weekend

[jira] [Commented] (HDFS-941) Datanode xceiver protocol should allow reuse of a connection

[ https://issues.apache.org/jira/browse/HDFS-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052166#comment-13052166 ] Konstantin Shvachko commented on HDFS-941: -- Answers to some issues raised here: St

[jira] [Updated] (HDFS-2018) Move all journal stream management code into one place

[ https://issues.apache.org/jira/browse/HDFS-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated HDFS-2018: - Attachment: HDFS-2018.diff Another rough patch, which I'll clean up tomorrow. In this patch, multiple jou

[jira] [Commented] (HDFS-2018) Move all journal stream management code into one place

[ https://issues.apache.org/jira/browse/HDFS-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052180#comment-13052180 ] Ivan Kelly commented on HDFS-2018: -- Forgot to mention, the cleanup I plan to do is to remo

[jira] [Commented] (HDFS-2018) Move all journal stream management code into one place

[ https://issues.apache.org/jira/browse/HDFS-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052183#comment-13052183 ] Hadoop QA commented on HDFS-2018: - -1 overall. Here are the results of testing the latest

[jira] [Created] (HDFS-2086) If the include hosts list contains host name, after restarting namenode, datanodes registrant is denied

If the include hosts list contains host name, after restarting namenode, datanodes registrant is denied Key: HDFS-2086 URL: https://issues.apache.org/jira/br

[jira] [Updated] (HDFS-2086) If the include hosts list contains host name, after restarting namenode, datanodes registrant is denied

[ https://issues.apache.org/jira/browse/HDFS-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanping Wang updated HDFS-2086: --- Component/s: name-node Affects Version/s: 0.23.0 Fix Version/s: 0.23.0 A

[jira] [Updated] (HDFS-2086) If the include hosts list contains host name, after restarting namenode, datanodes registrant is denied

[ https://issues.apache.org/jira/browse/HDFS-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanping Wang updated HDFS-2086: --- Description: As the title describes the problem: if the include host list contains host name, after

[jira] [Commented] (HDFS-2086) If the include hosts list contains host name, after restarting namenode, datanodes registrant is denied

[ https://issues.apache.org/jira/browse/HDFS-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052244#comment-13052244 ] Tanping Wang commented on HDFS-2086: There is a second part of this problem. When namen

[jira] [Created] (HDFS-2087) Add methods to DataTransferProtocol interface

Add methods to DataTransferProtocol interface - Key: HDFS-2087 URL: https://issues.apache.org/jira/browse/HDFS-2087 Project: Hadoop HDFS Issue Type: Sub-task Components: data-node, hdfs c

[jira] [Commented] (HDFS-2084) Sometimes backup node/secondary name node stops with exception

[ https://issues.apache.org/jira/browse/HDFS-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052248#comment-13052248 ] Konstantin Shvachko commented on HDFS-2084: --- Looks like the checkpoint contains a

[jira] [Commented] (HDFS-2083) Adopt JMXJsonServlet into HDFS in order to query statistics

[ https://issues.apache.org/jira/browse/HDFS-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052258#comment-13052258 ] Suresh Srinivas commented on HDFS-2083: --- # Minor: Make this a staic string? "/jmx?qr

[jira] [Created] (HDFS-2088) Move edits log archiving logic into FSEditLog/JournalManager

Move edits log archiving logic into FSEditLog/JournalManager Key: HDFS-2088 URL: https://issues.apache.org/jira/browse/HDFS-2088 Project: Hadoop HDFS Issue Type: Sub-task

[jira] [Commented] (HDFS-2018) Move all journal stream management code into one place

[ https://issues.apache.org/jira/browse/HDFS-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052262#comment-13052262 ] Todd Lipcon commented on HDFS-2018: --- Some comments on this patch: - general idea seems ri

[jira] [Updated] (HDFS-2088) Move edits log archiving logic into FSEditLog/JournalManager

[ https://issues.apache.org/jira/browse/HDFS-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-2088: -- Component/s: name-node Description: Currently the logic to archive edits logs is File-sp

[jira] [Updated] (HDFS-2088) Move edits log archiving logic into FSEditLog/JournalManager

[ https://issues.apache.org/jira/browse/HDFS-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-2088: -- Attachment: hdfs-2088.txt Patch does the following: - once StorageArchivalManager determines the minimum

[jira] [Commented] (HDFS-2088) Move edits log archiving logic into FSEditLog/JournalManager

[ https://issues.apache.org/jira/browse/HDFS-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052265#comment-13052265 ] Todd Lipcon commented on HDFS-2088: --- btw, the above patch sequences after the following:

[jira] [Updated] (HDFS-2086) If the include hosts list contains host name, after restarting namenode, datanodes registrant is denied

[ https://issues.apache.org/jira/browse/HDFS-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanping Wang updated HDFS-2086: --- Attachment: HDFS-2086.patch > If the include hosts list contains host name, after restarting namenode,

[jira] [Created] (HDFS-2089) new hadoop-config.sh doesn't manage classpath for HADOOP_CONF_DIR correctly

new hadoop-config.sh doesn't manage classpath for HADOOP_CONF_DIR correctly --- Key: HDFS-2089 URL: https://issues.apache.org/jira/browse/HDFS-2089 Project: Hadoop HDFS

[jira] [Updated] (HDFS-2086) If the include hosts list contains host name, after restarting namenode, datanodes registrant is denied

[ https://issues.apache.org/jira/browse/HDFS-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jitendra Nath Pandey updated HDFS-2086: --- Status: Patch Available (was: Open) > If the include hosts list contains host name, a

[jira] [Commented] (HDFS-2086) If the include hosts list contains host name, after restarting namenode, datanodes registrant is denied

[ https://issues.apache.org/jira/browse/HDFS-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052297#comment-13052297 ] Jitendra Nath Pandey commented on HDFS-2086: 1. inHostsList and inExcludeHostsL

[jira] [Commented] (HDFS-2082) SecondaryNameNode web interface doesn't show the right info

[ https://issues.apache.org/jira/browse/HDFS-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052299#comment-13052299 ] Hadoop QA commented on HDFS-2082: - -1 overall. Here are the results of testing the latest

[jira] [Commented] (HDFS-2082) SecondaryNameNode web interface doesn't show the right info

[ https://issues.apache.org/jira/browse/HDFS-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052303#comment-13052303 ] Aaron T. Myers commented on HDFS-2082: -- I'm pretty confident this test failure was spu

[jira] [Commented] (HDFS-2077) 1073: address checkpoint upload when one of the storage dirs is failed

[ https://issues.apache.org/jira/browse/HDFS-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052305#comment-13052305 ] Todd Lipcon commented on HDFS-2077: --- just found a good bug in this while doing some fault

[jira] [Updated] (HDFS-2087) Add methods to DataTransferProtocol interface

[ https://issues.apache.org/jira/browse/HDFS-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-2087: - Attachment: h2087_20110620.patch h2087_20110620.patch: added {{readBlock(..)}} onl

[jira] [Commented] (HDFS-2086) If the include hosts list contains host name, after restarting namenode, datanodes registrant is denied

[ https://issues.apache.org/jira/browse/HDFS-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052314#comment-13052314 ] Hadoop QA commented on HDFS-2086: - -1 overall. Here are the results of testing the latest

[jira] [Created] (HDFS-2090) BackupNode fails when log is streamed due checksum error

BackupNode fails when log is streamed due checksum error - Key: HDFS-2090 URL: https://issues.apache.org/jira/browse/HDFS-2090 Project: Hadoop HDFS Issue Type: Bug Components

[jira] [Commented] (HDFS-2090) BackupNode fails when log is streamed due checksum error

[ https://issues.apache.org/jira/browse/HDFS-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052321#comment-13052321 ] André Oriani commented on HDFS-2090: According to my investigation and the help of Ivan

[jira] [Commented] (HDFS-2090) BackupNode fails when log is streamed due checksum error

[ https://issues.apache.org/jira/browse/HDFS-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052322#comment-13052322 ] André Oriani commented on HDFS-2090: According to my investigation and the help of Ivan

[jira] [Commented] (HDFS-1568) Improve DataXceiver error logging

[ https://issues.apache.org/jira/browse/HDFS-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052339#comment-13052339 ] Hadoop QA commented on HDFS-1568: - -1 overall. Here are the results of testing the latest

[jira] [Created] (HDFS-2091) Hadoop does not scale as expected

Hadoop does not scale as expected - Key: HDFS-2091 URL: https://issues.apache.org/jira/browse/HDFS-2091 Project: Hadoop HDFS Issue Type: Bug Environment: Linux, 8 nodes. Reporter: Alberto

[jira] [Updated] (HDFS-2091) Hadoop does not scale as expected

[ https://issues.apache.org/jira/browse/HDFS-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Andreotti updated HDFS-2091: Description: The more nodes I add to this application, the slower it goes. This is the app's

[jira] [Resolved] (HDFS-2091) Hadoop does not scale as expected

[ https://issues.apache.org/jira/browse/HDFS-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved HDFS-2091. --- Resolution: Invalid Hi Alberto. This is the bug tracker rather than a place for questions. You might

[jira] [Created] (HDFS-2092) Remove configuration object reference in DFSClient

Remove configuration object reference in DFSClient -- Key: HDFS-2092 URL: https://issues.apache.org/jira/browse/HDFS-2092 Project: Hadoop HDFS Issue Type: Bug Components: hdfs client

[jira] [Created] (HDFS-2094) Add metrics for write pipeline failures

Add metrics for write pipeline failures --- Key: HDFS-2094 URL: https://issues.apache.org/jira/browse/HDFS-2094 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.23.0 Reporter: Bhara

[jira] [Commented] (HDFS-2093) 1073: Handle case where an entirely empty log is left during NN crash

[ https://issues.apache.org/jira/browse/HDFS-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052347#comment-13052347 ] Todd Lipcon commented on HDFS-2093: --- The really good news here is that the robustness of

[jira] [Updated] (HDFS-2093) 1073: Handle case where an entirely empty log is left during NN crash

[ https://issues.apache.org/jira/browse/HDFS-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-2093: -- Component/s: name-node Description: In fault-testing the HDFS-1073 branch, I saw the fol

[jira] [Created] (HDFS-2093) 1073: Handle case where an entirely empty log is left during NN crash

1073: Handle case where an entirely empty log is left during NN crash - Key: HDFS-2093 URL: https://issues.apache.org/jira/browse/HDFS-2093 Project: Hadoop HDFS Issue Type:

[jira] [Updated] (HDFS-2093) 1073: Handle case where an entirely empty log is left during NN crash

[ https://issues.apache.org/jira/browse/HDFS-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-2093: -- Attachment: hdfs-2093.txt Attached patch considers such logs as corrupt at startup time. Thus in the si

[jira] [Commented] (HDFS-2084) Sometimes backup node/secondary name node stops with exception

[ https://issues.apache.org/jira/browse/HDFS-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052360#comment-13052360 ] Vitalii Tymchyshyn commented on HDFS-2084: -- I dont know how does it happen, but it

[jira] [Updated] (HDFS-2093) 1073: Handle case where an entirely empty log is left during NN crash

[ https://issues.apache.org/jira/browse/HDFS-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-2093: -- Attachment: hdfs-2093.txt Updated patch addresses the case where the above happens and there is only on

[jira] [Updated] (HDFS-2080) Speed up DFS read path

[ https://issues.apache.org/jira/browse/HDFS-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-2080: -- Attachment: hdfs-2080.txt Updated patch to fix a couple of the issues mentioned above: - fix a couple of

[jira] [Updated] (HDFS-2077) 1073: address checkpoint upload when one of the storage dirs is failed

[ https://issues.apache.org/jira/browse/HDFS-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-2077: -- Attachment: hdfs-2077.txt Updated patch to fix the above dumb bug. > 1073: address checkpoint upload wh