1> surprising that your range scan times out. Could you share some insert row keys(after hashing) and start & stop rowkeys you are using to scan/query? Row keys design is very important, it has to match your retrieval pattern.
2> Yes, its Hbase is best as long you are doing range scan or to get key value pairs. On Sun, Oct 8, 2017 at 1:16 AM, Ted Yu <[email protected]> wrote: > What's the value for hbase.hregion.max.filesize ? > By default it is 10GB. > > bq. any other scan including startrow and stoprow > > Did the start / stop rows encompass the 3 regions ? > > Please also see http://hbase.apache.org/book.html#ops.date.tiered > > Cheers > > On Sat, Oct 7, 2017 at 9:59 AM, sauloricci <[email protected]> wrote: > > > I've designed HBase table where my rowkey is driven to the queries that I > > need to run on it. Following the best practices I included a hashed > portion > > as prefix of my rowkeys, trying to spread the rows as much uniform as > > possible across my table regions. > > > > I'm concerned about the following scenario: > > > > I got billions of rows in my HBase table split between 3 regions. I'm > using > > this table to provide data for a REST API, and because that, it needs to > > provide the rows as fast as possible. > > > > Unfortunately, I'm hitting the famous timeout error Failed to get result > > within timeout, timeout=60000ms even if I invoke either count > "table_name" > > in the hbase shell or for any other scan including startrow and stoprow > > parameters.It seems scanning by ranges using the rowkey is sweeping the > > whole hbase table. > > > > Considering this scenario I'd like to ask 2 questions: > > > > 1) Is there any strategy to really retrieve range of rows as fast as > > possible without hitting the timeout error? I really appreciate any > > pointers > > here. > > > > 2) As I'm new in HBase, do you think HBase is the best or at least > adequate > > solution to provide fast retrieval data to a REST API, considering the > > search are in fact scans by range of rowkeys? > > > > > > > > -- > > Sent from: http://apache-hbase.679495.n3.nabble.com/HBase-User- > > f4020416.html > > >
