HDFS side of HADOOP-6904: first step towards inter-version communications
between dfs client and NameNode
-
Key: HDFS-1335
URL:
[
https://issues.apache.org/jira/browse/HDFS-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakob Homan resolved HDFS-320.
--
Resolution: Won't Fix
Resolving as Won't Fix.
Namenode should return lease recovery request with other
TruncateBlock does not update in-memory information correctly
-
Key: HDFS-1336
URL: https://issues.apache.org/jira/browse/HDFS-1336
Project: Hadoop HDFS
Issue Type: Bug
Unmatched file length makes append fail. Should we retry if a
startBlockRecovery() fails?
-
Key: HDFS-1337
URL: https://issues.apache.org/jira/browse/HDFS-1337
Hi all,
I was studying the code of HDFS-976 and Dhruba's overview about Avatar Nodes
(
http://hadoopblog.blogspot.com/2010/02/hadoop-namenode-high-availability.html)
when some questions came to my mind. If I understood correctly, avatar
datanodes send heartbeats, block reports and block received
No, only the active namenode sends commands back to the datanodes in avatar
node setup.
On Aug 9, 2010, at 5:05 PM, André Oriani ra078...@students.ic.unicamp.br
wrote:
Hi all,
I was studying the code of HDFS-976 and Dhruba's overview about Avatar Nodes
(