hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-907) getScanner hangs with some startRows that are found if scanning entire table
Date Mon, 29 Sep 2008 18:28:44 GMT

    [ https://issues.apache.org/jira/browse/HBASE-907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12635472#action_12635472
] 

stack commented on HBASE-907:
-----------------------------

Our retry mechanism is masking real issue by throwing NPE on last retry.  Need to fix that.
 That said, anything earlier in the log Jon?  Dumb exception should at least say what the
problematic row was so could try it in client.

> getScanner hangs with some startRows that are found if scanning entire table
> ----------------------------------------------------------------------------
>
>                 Key: HBASE-907
>                 URL: https://issues.apache.org/jira/browse/HBASE-907
>             Project: Hadoop HBase
>          Issue Type: Bug
>    Affects Versions: 0.18.0, 0.18.1, 0.19.0
>            Reporter: Jonathan Gray
>            Priority: Critical
>             Fix For: 0.18.1, 0.19.0
>
>
> I have a table with 8 byte binary row keys.  There are a a few hundred thousands rows,
each with two families and between 1k and 50k of total data across about 15 columns.
> When attempting to get a scanner using a specified startRow, my client freezes on the
HT.getScanner(cols,row) with no exception ever thrown and no debug output in any server logs.
> If I get a scanner with HT.getScanner(cols) and then iterate through, I will eventually
reach the row I was seeking before successfully.
> Some rows can be found, some cannot.  At this point I'm not able to distinguish anything
special about the ones that cause the client the hang.
> At first I thought this was only a problem with 0.19 trunk as a downgrade to 0.18 resolved
the issue for a particular key.  However other keys still have this issue on 0.18 branch.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message