[jira] Commented: (HBASE-907) getScanner hangs with some startRows that are found if scanning entire table

["Jonathan Gray (JIRA)" <ji...@apache.org>]

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

Jonathan Gray commented on HBASE-907:
-------------------------------------

No longer able to recreate issue.

Things have changed in the client code that triggered this.  Still unsure whether there was a bug in the client (not really sure how it would make rows visible with one method and not the other) or I have not gotten the table as big as it was when I experienced this.

Would like to wait another week or two before closing this issue.  Definitely not a blocker at this point though.

> 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.