>
>
> A few questions:
> - Do we have a clear definition for a cluster?
>
Cluster before federation is defined by list of datanodes in include file,
bound together by namespaceID of the namenode that these nodes bind to on
first registration with the namenode. In essence, namespaceID defines the
>
> But this does make things easier. Although I'm still fairly
> confident that it adds too much complexity for little gain though.
Allen,can you please add details on what complexity you are talking about
here? (I have already asked this question many times)
>From code perspective it
See https://hudson.apache.org/hudson/job/Hadoop-Hdfs-trunk/616/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 708649 lines...]
[junit] 2011-03-24 12:22:35,34
Hello,
I've done some initial work for making the volume-block choosing
policy pluggable (so that methods other than round-robin may be
provided).
The following is my initial interface design, and am looking for
comments/critique/etc. w.r.t.
https://issues.apache.org/jira/browse/HDFS-1120's scope
[
https://issues.apache.org/jira/browse/HDFS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsz Wo (Nicholas), SZE resolved HDFS-1773.
--
Resolution: Fixed
Fix Version/s: (was: 0.20.4)
0.20
jsvc executable delivered into wrong package...
---
Key: HDFS-1781
URL: https://issues.apache.org/jira/browse/HDFS-1781
Project: Hadoop HDFS
Issue Type: Bug
Affects Versions: 0.22.0
FSNamesystem.startFileInternal(..) throws NullPointerException
--
Key: HDFS-1782
URL: https://issues.apache.org/jira/browse/HDFS-1782
Project: Hadoop HDFS
Issue Type: Bug
Affect
Ability for HDFS client to write replicas in parallel
-
Key: HDFS-1783
URL: https://issues.apache.org/jira/browse/HDFS-1783
Project: Hadoop HDFS
Issue Type: Improvement
Components
Cleanup BlockReceiver and DataXceiver
-
Key: HDFS-1785
URL: https://issues.apache.org/jira/browse/HDFS-1785
Project: Hadoop HDFS
Issue Type: Improvement
Components: data-node
Reporter