[
https://issues.apache.org/jira/browse/HBASE-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthik Pandian updated HBASE-5322:
-----------------------------------
Description:
I have a hbase table which holds data for more than 10GB. Now I used the same
client scanner to scan which fails and reports,
"Could not seek StoreFileScanner[HFileScanner for reader reader=hdfs".
This issue occurs only for the table which holds huge data and not for tables
holding small data.
was:
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.
Priority: Blocker (was: Critical)
Affects Version/s: (was: 0.18.1)
(was: 0.19.0)
(was: 0.18.0)
0.90.4
Fix Version/s: (was: 0.18.1)
(was: 0.19.0)
> CLONE - getScanner hangs with some startRows that are found if scanning
> entire table
> ------------------------------------------------------------------------------------
>
> Key: HBASE-5322
> URL: https://issues.apache.org/jira/browse/HBASE-5322
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.90.4
> Reporter: Karthik Pandian
> Priority: Blocker
>
> I have a hbase table which holds data for more than 10GB. Now I used the same
> client scanner to scan which fails and reports,
> "Could not seek StoreFileScanner[HFileScanner for reader reader=hdfs".
> This issue occurs only for the table which holds huge data and not for tables
> holding small data.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
