[jira] [Created] (HDFS-2050) Backup name node stops responding

Backup name node stops responding - Key: HDFS-2050 URL: https://issues.apache.org/jira/browse/HDFS-2050 Project: Hadoop HDFS Issue Type: Bug Components: name-node Affects Versions: 0.21.0

[jira] [Updated] (HDFS-2003) Separate FSEditLog reading logic from editLog memory state building logic

[ https://issues.apache.org/jira/browse/HDFS-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated HDFS-2003: - Attachment: HDFS-2003-replicationfix-delta.diff Separate FSEditLog reading logic from editLog memory

[jira] [Updated] (HDFS-2003) Separate FSEditLog reading logic from editLog memory state building logic

[ https://issues.apache.org/jira/browse/HDFS-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated HDFS-2003: - Attachment: HDFS-2003.diff Separate FSEditLog reading logic from editLog memory state building logic

[jira] [Commented] (HDFS-2003) Separate FSEditLog reading logic from editLog memory state building logic

[ https://issues.apache.org/jira/browse/HDFS-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13045954#comment-13045954 ] Ivan Kelly commented on HDFS-2003: -- Fixed the reading of blocks so that replication is

[jira] [Commented] (HDFS-2003) Separate FSEditLog reading logic from editLog memory state building logic

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

[jira] [Updated] (HDFS-2003) Separate FSEditLog reading logic from editLog memory state building logic

[ https://issues.apache.org/jira/browse/HDFS-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated HDFS-2003: - Attachment: HDFS-2003.diff Resubmitting patch fixing error which caused hudson failure. As reading in the

[jira] [Updated] (HDFS-2040) Only build libhdfs if a flag is passed

[ https://issues.apache.org/jira/browse/HDFS-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-2040: -- Resolution: Fixed Status: Resolved (was: Patch Available) I've committed this. Thanks Eric and

[jira] [Created] (HDFS-2051) TestBlockRecovery.testErrorReplicas is timing out

TestBlockRecovery.testErrorReplicas is timing out - Key: HDFS-2051 URL: https://issues.apache.org/jira/browse/HDFS-2051 Project: Hadoop HDFS Issue Type: Bug Components: data-node

[jira] [Commented] (HDFS-2030) Fix the usability of namenode upgrade command

[ https://issues.apache.org/jira/browse/HDFS-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13046081#comment-13046081 ] Suresh Srinivas commented on HDFS-2030: --- # TestFSImageUpgrade #* is missing banner.

[jira] [Commented] (HDFS-2003) Separate FSEditLog reading logic from editLog memory state building logic

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

[jira] [Resolved] (HDFS-1878) TestHDFSServerPorts unit test failure - race condition in FSNamesystem.close() causes NullPointerException without serious consequence

[ https://issues.apache.org/jira/browse/HDFS-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Foley resolved HDFS-1878. -- Resolution: Fixed Committed to 0.20-security and 0.20-security-205. TestHDFSServerPorts unit test

[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-tabpanelfocusedCommentId=13046148#comment-13046148 ] stack commented on HDFS-941: +1 on commit. Have run this patch first in a light random read

[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-tabpanelfocusedCommentId=13046151#comment-13046151 ] stack commented on HDFS-941: Oh, just to say that I don't seem hdfs-level complaints in server

[jira] [Updated] (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:all-tabpanel ] stack updated HDFS-941: --- Attachment: HDFS-941-6.22.patch Here is version of patch that applies to 0.22; a couple of imports and constants were

[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-tabpanelfocusedCommentId=13046155#comment-13046155 ] stack commented on HDFS-941: This patch should be applied to hadoop 0.22. It'd be an incentive

[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-tabpanelfocusedCommentId=13046159#comment-13046159 ] Todd Lipcon commented on HDFS-941: -- Stack, thanks a million for the cluster testing and

[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-tabpanelfocusedCommentId=13046162#comment-13046162 ] stack commented on HDFS-941: On occasion I see these new additions to the datanode log: {code}

[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-tabpanelfocusedCommentId=13046175#comment-13046175 ] Todd Lipcon commented on HDFS-941: -- Hey Stack, are you sure you got the latest patch

[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-tabpanelfocusedCommentId=13046182#comment-13046182 ] stack commented on HDFS-941: OK. Looks like I was running the just-previous. Let me redo

[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-tabpanelfocusedCommentId=13046183#comment-13046183 ] stack commented on HDFS-941: Or, hang on, let me indeed verify 0.22 has this minus the 941

[jira] [Commented] (HDFS-2003) Separate FSEditLog reading logic from editLog memory state building logic

[ https://issues.apache.org/jira/browse/HDFS-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13046187#comment-13046187 ] Todd Lipcon commented on HDFS-2003: --- bq. @Todd could you give this a quick test with your

[jira] [Commented] (HDFS-1333) S3 File Permissions

[ https://issues.apache.org/jira/browse/HDFS-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13046202#comment-13046202 ] Wouter de Bie commented on HDFS-1333: - I've experienced the same error on 0.20.2

[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-tabpanelfocusedCommentId=13046212#comment-13046212 ] Kihwal Lee commented on HDFS-941: - I will try putting some load in a cluster with this patch

[jira] [Updated] (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:all-tabpanel ] Todd Lipcon updated HDFS-941: - Attachment: hdfs-941.txt New patch with response to stack's review: bq. ... google-collections ... I

[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-tabpanelfocusedCommentId=13046234#comment-13046234 ] stack commented on HDFS-941: New patch looks good (nice comment on why NODELAY). Let me test

[jira] [Updated] (HDFS-1295) Improve namenode restart times by short-circuiting the first block reports from datanodes

[ https://issues.apache.org/jira/browse/HDFS-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Foley updated HDFS-1295: - Attachment: HDFS-1295_delta_for_trunk.patch Delta patch to re-integrate HDFS-1295 with DataNode.java in

[jira] [Updated] (HDFS-1295) Improve namenode restart times by short-circuiting the first block reports from datanodes

[ https://issues.apache.org/jira/browse/HDFS-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Foley updated HDFS-1295: - Affects Version/s: (was: 0.22.0) 0.23.0 Hadoop Flags: (was:

[jira] [Created] (HDFS-2052) FSNamesystem should not sync the log with the write lock held

FSNamesystem should not sync the log with the write lock held - Key: HDFS-2052 URL: https://issues.apache.org/jira/browse/HDFS-2052 Project: Hadoop HDFS Issue Type: Improvement

[jira] [Commented] (HDFS-978) Record every new block allocation of a file into the transaction log.

[ https://issues.apache.org/jira/browse/HDFS-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13046283#comment-13046283 ] Eli Collins commented on HDFS-978: -- FSNameSystem#getAdditionalBlock currently doesn't sync

[jira] [Updated] (HDFS-1580) Add interface for generic Write Ahead Logging mechanisms

[ https://issues.apache.org/jira/browse/HDFS-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jitendra Nath Pandey updated HDFS-1580: --- Attachment: EditlogInterface.3.pdf The latest design document introduces JournalSet

[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-tabpanelfocusedCommentId=13046311#comment-13046311 ] Hadoop QA commented on HDFS-941: -1 overall. Here are the results of testing the latest

[jira] [Commented] (HDFS-1295) Improve namenode restart times by short-circuiting the first block reports from datanodes

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

[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-tabpanelfocusedCommentId=13046330#comment-13046330 ] Todd Lipcon commented on HDFS-941: -- I'd like to commit this tomorrow so long as Stack and

[jira] [Commented] (HDFS-1690) Name Node should not process format command while it is running.

[ https://issues.apache.org/jira/browse/HDFS-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13046348#comment-13046348 ] Uma Maheswara Rao G commented on HDFS-1690: --- Thanks for your comments sorry for

[jira] [Commented] (HDFS-1973) HA: HDFS clients must handle namenode failover and switch over to the new active namenode.

[ https://issues.apache.org/jira/browse/HDFS-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13046352#comment-13046352 ] Hari A V commented on HDFS-1973: Hi Aron, Can you please elaborate a little bit on your