[jira] Created: (HDFS-1620) FSConstants vs FsConstants

FSConstants vs FsConstants --- Key: HDFS-1620 URL: https://issues.apache.org/jira/browse/HDFS-1620 Project: Hadoop HDFS Issue Type: Improvement Reporter: Tsz Wo (Nicholas), SZE Priority:

[jira] Created: (HDFS-1621) Fix references to hadoop-common-${version} in build.xml

Fix references to hadoop-common-${version} in build.xml --- Key: HDFS-1621 URL: https://issues.apache.org/jira/browse/HDFS-1621 Project: Hadoop HDFS Issue Type: Bug Reporter:

[jira] Commented: (HDFS-1573) LeaseChecker thread name trace not that useful

[ https://issues.apache.org/jira/browse/HDFS-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12992934#comment-12992934 ] Tsz Wo (Nicholas), SZE commented on HDFS-1573: -- Is this already fixed by now?

[jira] Updated: (HDFS-1606) Provide a stronger data guarantee in the write pipeline

[ https://issues.apache.org/jira/browse/HDFS-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-1606: - Attachment: h1606_20110210.patch h1606_20110210.patch: - Adding

[jira] Commented: (HDFS-1573) LeaseChecker thread name trace not that useful

[ https://issues.apache.org/jira/browse/HDFS-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12993105#comment-12993105 ] Todd Lipcon commented on HDFS-1573: --- I don't think so. I had a patch around somewhere,

[jira] Commented: (HDFS-347) DFS read performance suboptimal when client co-located on nodes with data

[ https://issues.apache.org/jira/browse/HDFS-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12993109#comment-12993109 ] Allen Wittenauer commented on HDFS-347: --- Short Story: I need to look at the patch but

[jira] Commented: (HDFS-347) DFS read performance suboptimal when client co-located on nodes with data

[ https://issues.apache.org/jira/browse/HDFS-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12993153#comment-12993153 ] Owen O'Malley commented on HDFS-347: Allen, the question is more whether passing fds

[jira] Commented: (HDFS-347) DFS read performance suboptimal when client co-located on nodes with data

[ https://issues.apache.org/jira/browse/HDFS-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12993155#comment-12993155 ] Jonathan Gray commented on HDFS-347: A very large percentage of reads are local in

[jira] Commented: (HDFS-347) DFS read performance suboptimal when client co-located on nodes with data

[ https://issues.apache.org/jira/browse/HDFS-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12993156#comment-12993156 ] stack commented on HDFS-347: @Owen Remote reads are the exception. DFS read performance

[jira] Commented: (HDFS-347) DFS read performance suboptimal when client co-located on nodes with data

[ https://issues.apache.org/jira/browse/HDFS-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12993157#comment-12993157 ] Todd Lipcon commented on HDFS-347: -- bq. One thing that absolutely needs to be checked is

[jira] Commented: (HDFS-347) DFS read performance suboptimal when client co-located on nodes with data

[ https://issues.apache.org/jira/browse/HDFS-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12993179#comment-12993179 ] dhruba borthakur commented on HDFS-347: --- almost all reads ( 99%) in hbase are

[jira] Assigned: (HDFS-1622) Update TestDFSUpgradeFromImage to test batch hardlink improvment

[ https://issues.apache.org/jira/browse/HDFS-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hairong Kuang reassigned HDFS-1622: --- Assignee: Hairong Kuang Update TestDFSUpgradeFromImage to test batch hardlink improvment

[jira] Created: (HDFS-1622) Update TestDFSUpgradeFromImage to test batch hardlink improvment

Update TestDFSUpgradeFromImage to test batch hardlink improvment Key: HDFS-1622 URL: https://issues.apache.org/jira/browse/HDFS-1622 Project: Hadoop HDFS Issue Type:

[jira] Commented: (HDFS-1602) Fix HADOOP-4885 for it is doesn't work as expected.

[ https://issues.apache.org/jira/browse/HDFS-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12993216#comment-12993216 ] Hudson commented on HDFS-1602: -- Integrated in Hadoop-Hdfs-trunk-Commit #540 (See

[jira] Updated: (HDFS-1618) configure files that are generated as part of the released tarball need to have executable bit set

[ https://issues.apache.org/jira/browse/HDFS-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Shaposhnik updated HDFS-1618: --- Status: Patch Available (was: Open) configure files that are generated as part of the

[jira] Commented: (HDFS-1143) Implement Background deletion

[ https://issues.apache.org/jira/browse/HDFS-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12993260#comment-12993260 ] Suresh Srinivas commented on HDFS-1143: --- Blocks collected from the detached inode are

[jira] Commented: (HDFS-1143) Implement Background deletion

[ https://issues.apache.org/jira/browse/HDFS-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12993261#comment-12993261 ] Suresh Srinivas commented on HDFS-1143: --- Blocks collected from the detached inode

[jira] Commented: (HDFS-1109) HFTP and URL Encoding

[ https://issues.apache.org/jira/browse/HDFS-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12993264#comment-12993264 ] Jitendra Nath Pandey commented on HDFS-1109: Dmytro, Is there a separate jira

[jira] Commented: (HDFS-1618) configure files that are generated as part of the released tarball need to have executable bit set

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

[jira] Resolved: (HDFS-875) NameNode incorretly handles corrupt replicas

[ https://issues.apache.org/jira/browse/HDFS-875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko resolved HDFS-875. -- Resolution: Duplicate Resolving as duplicate of HDFS-900. Feel free to reopen if there

[jira] Resolved: (HDFS-1496) TestStorageRestore is failing after HDFS-903 fix

[ https://issues.apache.org/jira/browse/HDFS-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko resolved HDFS-1496. --- Resolution: Fixed Fixed by HDFS-1602. TestStorageRestore is failing after HDFS-903

[jira] Created: (HDFS-1623) High Availability Framework for HDFS NN

High Availability Framework for HDFS NN --- Key: HDFS-1623 URL: https://issues.apache.org/jira/browse/HDFS-1623 Project: Hadoop HDFS Issue Type: New Feature Reporter: Sanjay Radia

[jira] Commented: (HDFS-1623) High Availability Framework for HDFS NN

[ https://issues.apache.org/jira/browse/HDFS-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12993315#comment-12993315 ] Sanjay Radia commented on HDFS-1623: There are various steps one can take to improve

[jira] Updated: (HDFS-1623) High Availability Framework for HDFS NN

[ https://issues.apache.org/jira/browse/HDFS-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HDFS-1623: --- Attachment: Namenode HA Framework.pdf Draft of Proposal High Availability Framework for HDFS NN

[jira] Commented: (HDFS-1606) Provide a stronger data guarantee in the write pipeline

[ https://issues.apache.org/jira/browse/HDFS-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12993330#comment-12993330 ] Tsz Wo (Nicholas), SZE commented on HDFS-1606: -- Below are the proposed new