Sent: Fri, May 13, 2011 12:39 am
Subject: Re: mapreduce job failure
All that means is that the task stayed in map() for 10 minutes,
blocked on something.
If you were scanning an hbase table, and didn't get a new row after 1
minute, then the scanner would expire. That's orthogonal tho
thanks J-D as always
-Original Message-
From: Jean-Daniel Cryans jdcry...@apache.org
To: user@hbase.apache.org
Sent: Tue, May 17, 2011 8:04 pm
Subject: Re: mapreduce job failure
400 regions a day is way too much, also in 0.20.6 there's a high risk
of collision when you get
jdcry...@apache.org
To: user@hbase.apache.org
Sent: Fri, May 13, 2011 12:39 am
Subject: Re: mapreduce job failure
All that means is that the task stayed in map() for 10 minutes,
blocked on something.
If you were scanning an hbase table, and didn't get a new row after 1
minute
Hi
Using hbase-0.20.6
mapreduce job started failing in the map phase (using hbase table as input for
mapper)..(ran fine for a week or so starting with empty tables)..
task tracker log:
Task attempt_201105121141_0002_m_000452_0 failed to report status for 600
seconds. Killing
Region
