Hi,
Talking to Lars we found a weird series of events that led to dying
task attempts during the bulk job they are running. See the attached
log. Region in question is:
raw_occurrence_record,28256992928,1290626317732.86e3cd5c5d0f22430debb36f1668d3fc
After a split the region is assigned to a new
Lars:
Did you forget to attach the log (pastebin) ?
I assume this scenario could happen in 0.20.6 as well.
On Thu, Nov 25, 2010 at 2:49 AM, Lars George wrote:
> Hi,
>
> Talking to Lars we found a weird series of events that led to dying
> task attempts during the bulk job they are running. See
Apparently it got stripped. My GMail webclient shows it though but
that seems misleading. Here is the log:
http://pastebin.com/pLDp9p0D
Lars
On Thu, Nov 25, 2010 at 3:59 PM, Ted Yu wrote:
> Lars:
> Did you forget to attach the log (pastebin) ?
>
> I assume this scenario could happen in 0.20.6 a
Does hbase-dev still get forwarded? Did you see the below message?
-- Forwarded message --
From: Lars George
Date: Tue, Nov 23, 2010 at 4:25 PM
Subject: HRegion.RegionScanner.nextInternal()
To: hbase-...@hadoop.apache.org
Hi,
I am officially confused:
byte [] nextRow;
limit is for retrieving partial results of a row. Ie: give me a row
in chunks. Filters that want to operate on the entire row cannot be
used with this mode. i forget why it's in the loop but there was a
good reason at the time.
-ryan
On Thu, Nov 25, 2010 at 10:51 AM, Lars George wrote:
> Does
Mkay, I will look into it more for the latter. But for the limit this is still
confusing to me as limit == batch and that is in he client side the number of
rows. But not the number of columns. Does that mean if I had 100 columns and
set batch to 10 that it would only return 10 rows with 10 colu
No, batch size when limit is set is 1. You get partial results for a route,
then get more from the same row. Then the next row.
On Nov 25, 2010 4:54 PM, "Lars George" wrote:
> Mkay, I will look into it more for the latter. But for the limit this is
still confusing to me as limit == batch and that
