[jira] Commented: (HDFS-839) The NameNode should forward block reports to BackupNode

[ https://issues.apache.org/jira/browse/HDFS-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12801701#action_12801701 ] dhruba borthakur commented on HDFS-839: --- t seems like the network overhead of having

[jira] Commented: (HDFS-839) The NameNode should forward block reports to BackupNode

[ https://issues.apache.org/jira/browse/HDFS-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12801705#action_12801705 ] dhruba borthakur commented on HDFS-839: --- However, if it only synchronizes block

[jira] Commented: (HDFS-839) The NameNode should forward block reports to BackupNode

[ https://issues.apache.org/jira/browse/HDFS-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12801712#action_12801712 ] Wang Xu commented on HDFS-839: -- For multiple BN, I think pipeline is unacceptable in

[jira] Commented: (HDFS-839) The NameNode should forward block reports to BackupNode

[ https://issues.apache.org/jira/browse/HDFS-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12801718#action_12801718 ] Todd Lipcon commented on HDFS-839: -- Dhruba: regarding NN performance, do you often find that

[jira] Updated: (HDFS-630) In DFSOutputStream.nextBlockOutputStream(), the client can exclude specific datanodes when locating the next block.

[ https://issues.apache.org/jira/browse/HDFS-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cosmin Lehene updated HDFS-630: --- Status: Patch Available (was: Open) In DFSOutputStream.nextBlockOutputStream(), the client can

[jira] Updated: (HDFS-630) In DFSOutputStream.nextBlockOutputStream(), the client can exclude specific datanodes when locating the next block.

[ https://issues.apache.org/jira/browse/HDFS-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cosmin Lehene updated HDFS-630: --- Status: Open (was: Patch Available) tests fail erratically canceling again In

[jira] Commented: (HDFS-630) In DFSOutputStream.nextBlockOutputStream(), the client can exclude specific datanodes when locating the next block.

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

[jira] Created: (HDFS-905) Make changes to HDFS for the new UserGroupInformation APIs (HADOOP-6299)

Make changes to HDFS for the new UserGroupInformation APIs (HADOOP-6299) Key: HDFS-905 URL: https://issues.apache.org/jira/browse/HDFS-905 Project: Hadoop HDFS Issue

[jira] Commented: (HDFS-872) DFSClient 0.20.1 is incompatible with HDFS 0.20.2

[ https://issues.apache.org/jira/browse/HDFS-872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12801948#action_12801948 ] Todd Lipcon commented on HDFS-872: -- Do you have a good test case that can reproduce

[jira] Commented: (HDFS-839) The NameNode should forward block reports to BackupNode

[ https://issues.apache.org/jira/browse/HDFS-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12801973#action_12801973 ] dhruba borthakur commented on HDFS-839: --- Todd: I agree that CPU is not what I am

[jira] Commented: (HDFS-839) The NameNode should forward block reports to BackupNode

[ https://issues.apache.org/jira/browse/HDFS-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12801976#action_12801976 ] Todd Lipcon commented on HDFS-839: -- I see your point about additional memory pressure for

[jira] Commented: (HDFS-839) The NameNode should forward block reports to BackupNode

[ https://issues.apache.org/jira/browse/HDFS-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12801985#action_12801985 ] dhruba borthakur commented on HDFS-839: --- the all-through-the-NN solution can simply

[jira] Commented: (HDFS-839) The NameNode should forward block reports to BackupNode

[ https://issues.apache.org/jira/browse/HDFS-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12802028#action_12802028 ] Wang Xu commented on HDFS-839: -- todd, dhruba: as our practice, the duration of global lock does

[jira] Created: (HDFS-906) Remove MapReduce jars from raid lib directory

Remove MapReduce jars from raid lib directory - Key: HDFS-906 URL: https://issues.apache.org/jira/browse/HDFS-906 Project: Hadoop HDFS Issue Type: Bug Components: contrib/raid

[jira] Updated: (HDFS-902) TestRaidNode fails

[ https://issues.apache.org/jira/browse/HDFS-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HDFS-902: -- Component/s: contrib/raid TestRaidNode fails -- Key:

[jira] Resolved: (HDFS-906) Remove MapReduce jars from raid lib directory

[ https://issues.apache.org/jira/browse/HDFS-906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan resolved HDFS-906. -- Resolution: Duplicate Dhruba- Yep, different symptoms, but same cause. Closing as duplicate. Remove

[jira] Updated: (HDFS-902) TestRaidNode fails

[ https://issues.apache.org/jira/browse/HDFS-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-902: - Attachment: hdfs-902.patch Patch attached. It removes the marped jars that are checked in and adds the

[jira] Updated: (HDFS-902) TestRaidNode fails

[ https://issues.apache.org/jira/browse/HDFS-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-902: - Status: Patch Available (was: Open) TestRaidNode fails -- Key: