Sorry if this is a basic question. How does hbase determine which
regionserver the rows are supposed to be stored on? My rowkey looks like
hash_servername_timestamp, e.g.
33_myserver.mydomain.com_1234567890
If I run the following command:
scan 'dbi_based_data', {FILTER => "PrefixFilter('0')", COLUMNS =>
'raw_data:processlist', TIMERANGE => [1499205600000, 1499206200000]}
I get all the rows that start with "0". Since hbase stores things in
lexical order, it seems like all rows that were stored lexically first gets
returned.
However, if I run the following command, hbase times out. Even if I extend
the timeout period to 3 minutes, it still times out.
scan 'dbi_based_data', {FILTER => "PrefixFilter('28')", COLUMNS =>
'raw_data:processlist', TIMERANGE => [1499205600000, 1499206200000]}
It seems like if it was any other prefix other than "0", it times out (like
above prefix = 28). I don't understand why it would timeout since it
should be able to calculate which region/regionserver it should go to since
I gave it the prefix to use.
I performed "hbase hbck" and it says that
9 region servers are alive, 2 are dead
# of total regions is 15850 for the db but there's only 350 for the table
I'm querying. There are 0 inconsistencies so the status is "OK".
Thanks in advance for any help you can give me.
