[
https://issues.apache.org/jira/browse/HDFS-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Noguchi reopened HDFS-157:
---
bq. Hairong just opened a better Jira. HADOOP:6732
This didn't change the memory footprint on the client s
One bad node can incorrectly flag many files as corrupt
---
Key: HDFS-1371
URL: https://issues.apache.org/jira/browse/HDFS-1371
Project: Hadoop HDFS
Issue Type: Bug
Components: hd
HDFS-457 increases the chances of losing blocks
Key: HDFS-1158
URL: https://issues.apache.org/jira/browse/HDFS-1158
Project: Hadoop HDFS
Issue Type: Bug
Components: data-node
Af
[
https://issues.apache.org/jira/browse/HDFS-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Noguchi resolved HDFS-157.
---
Resolution: Duplicate
Hairong just opened a better Jira. HADOOP:6732
Thanks!
> dfs client -ls/-lsr out
[
https://issues.apache.org/jira/browse/HDFS-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Noguchi resolved HDFS-1102.
Resolution: Duplicate
Duplicate of HDFS-1085. It would be nice if we can fix this without changing
hftp read failing silently
---
Key: HDFS-1085
URL: https://issues.apache.org/jira/browse/HDFS-1085
Project: Hadoop HDFS
Issue Type: Bug
Reporter: Koji Noguchi
When performing a massive distcp through hf
[
https://issues.apache.org/jira/browse/HDFS-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Noguchi resolved HDFS-23.
--
Resolution: Duplicate
I'm hoping HDFS-985 is our answer.
No more chasing down users hitting namenode with
[
https://issues.apache.org/jira/browse/HDFS-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Noguchi resolved HDFS-304.
---
Resolution: Duplicate
This was fixed as part of https://issues.apache.org/jira/browse/HADOOP-4029
"Nam