+1 for 0.21.0
J-D
On Mon, Dec 14, 2009 at 11:30 PM, Andrew Purtell wrote:
> +1
>
>
> On Sat, Dec 12, 2009 at 3:54 PM, stack wrote:
>
>> HDFS-630 is kinda critical to us over in hbase. We'd like to get it into
>> 0.21 (Its been committed to TRUNK). Its probably hard to argue its a
>> blocker f
+1
Looks like the patch would apply cleanly. Have you guys done any
testing on 21 with it?
Thanks,
Eli
I'd like to propose a vote on having hdfs-630 committed to 0.21 (Its already
been committed to TRUNK).
hdfs-630 adds having the dfsclient pass the namenode the name of datanodes
its determined dead because it got a failed connection when it tried to
contact it, etc. This is useful in the interval
If HDFS-630 is a blocker for hbase on small clusters, maybe we can target it
for 0.21. Maybe you can run a VOTE for it?
thanks,
dhruba
On Sat, Dec 12, 2009 at 3:54 PM, stack wrote:
> HDFS-630 is kinda critical to us over in hbase. We'd like to get it into
> 0.21 (Its been committed to TRUNK).
blocksWritten metric is double-incremented for blocks received via replication
--
Key: HDFS-828
URL: https://issues.apache.org/jira/browse/HDFS-828
Project: Hadoop HDFS
Additional unit tests for FSDataset
---
Key: HDFS-827
URL: https://issues.apache.org/jira/browse/HDFS-827
Project: Hadoop HDFS
Issue Type: Test
Components: data-node, test
Affects Versions: 0.21.
