FWIW, not that I have a dog in this fight, but the only release with a
4th number (not including .0 like the 0.20.20x releases did) we had
was:
http://hadoop.6.n7.nabble.com/VOTE-Release-0-17-2-1-rc-0-td13398.html
0.17.2 was missing some native libs so 0.17.2.1 was released to fix
that critical i
Jean-Daniel Cryans created HDFS-4137:
Summary: BlockManager.chooseTarget's error message can be
confusing
Key: HDFS-4137
URL: https://issues.apache.org/jira/browse/HDFS-4137
Project: Hadoop
>From this page: http://hadoop.apache.org/hdfs/mailing_lists.html
Write an email to: hdfs-dev-unsubscr...@hadoop.apache.org
J-D
On Tue, Jun 12, 2012 at 4:26 PM, plova...@associatedrecruiters.net
wrote:
> Please unsubscribe me from your list
>
> Paul Lovallo
>
> Associated Recruiters
> 678.445.7
-2757
Project: Hadoop HDFS
Issue Type: Bug
Affects Versions: 1.0.0
Reporter: Jean-Daniel Cryans
Fix For: 1.1.0
When testing the tail'ing of a local file with the read short circuit on, I get:
{noformat}
2012-01-06 00:17:31,598 WARN org.apache.hadoop.hdfs
: 0.20.2
Reporter: Jean-Daniel Cryans
Priority: Trivial
Fix For: 0.22.0
DataXceiver will log an IOE twice because opReadBlock() will catch it, log a
WARN, then throw it again only to be caught in run() as a Throwable and logged
as an ERROR. As far as I can tell
+1
J-D
On Fri, Apr 2, 2010 at 10:38 AM, Stack wrote:
> Please on committing HDFS-1024 to the hadoop 0.20 branch.
>
> Background:
>
> HDFS-1024 fixes possible trashing of fsimage because of failed copy
> from 2NN and NN. Ordinarily, possible corruption of this proportion
> would merit commit w/o
+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
